Cross-source identifiers
Every current identifier attachment, with the link method and confidence carried verbatim — deterministic links are 1.000; probabilistic links surface their real matcher confidence, never rounded up.
| Scheme | Value | Source table | Link method | Confidence | Since | Provenance |
|---|---|---|---|---|---|---|
| pac_id | 0941666333 | snf_all_owners | deterministic_pac_in_all_owners | 1.000 | 2026-06-14 | evidencerecorded: 2026-06-14 methodology: entity-graph/v1 evidence: {"rule":"D-OWNER","source_pk":23519,"type_owner":"I","enrollment_id":"O20041015000691"} |
Graph edges
One-hop relationships — ownership, chain membership, operation — each backed by a federal source row.
| Relationship | Entity | Confidence | Source table | Provenance |
|---|---|---|---|---|
| owns → | VAN RUE INC. (OH) | 1.000 | snf_all_owners | evidencerecorded: 2026-06-16 methodology: entity-graph/v1 attributes: {"role_code":"34","association_date":"01/01/2020","percentage_ownership":35.14} evidence: {"rule":"D-OWNER","owner_pac":"0941666333","source_pk":23519,"type_owner":"I","enrollment_id":"O20041015000691","role_code_owner":"34","role_text_owner":"5% OR GREATER DIRECT OWNERSHIP INTEREST","dst_resolved_via":"pecos_enrlmt_id","percentage_ownership_raw":35.14,"enrollment_organization_name":"VAN RUE, INC."} |
| owns → | VANCREST OF TROY LLC (OH) | 1.000 | snf_all_owners | evidencerecorded: 2026-06-16 methodology: entity-graph/v1 attributes: {"role_code":"34","association_date":"12/30/2024","percentage_ownership":5} evidence: {"rule":"D-OWNER","owner_pac":"0941666333","source_pk":270554,"type_owner":"I","enrollment_id":"O20250505001233","role_code_owner":"34","role_text_owner":"5% OR GREATER DIRECT OWNERSHIP INTEREST","dst_resolved_via":"pecos_enrlmt_id","percentage_ownership_raw":5,"enrollment_organization_name":"VANCREST OF TROY, LLC"} |
Current record
Current claims returned for this entity, grouped by provenance subject. The table exposes the source identifier recorded for each claim.
Point-in-time
Query retained claim coordinates under bitemporal-read/v1. Most facts have no superseded row; dates outside retained coverage may return no prior version, and diffs require both coordinates.
Pick a date to reconstruct, or two dates to diff. Equivalent JSON: /api/v1/history/{subject_type}/{subject_id}?at=… and …/diff?from=…&to=…