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 | 2668900119 | 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":264297,"type_owner":"O","enrollment_id":"O20250108002715"} |
Graph edges
One-hop relationships — ownership, chain membership, operation — each backed by a federal source row.
| Relationship | Entity | Confidence | Source table | Provenance |
|---|---|---|---|---|
| owns → | BH CHESHIRE LLC (CT) | 1.000 | snf_all_owners | evidencerecorded: 2026-06-16 methodology: entity-graph/v1 attributes: {"role_code":"72","association_date":"01/13/2025","percentage_ownership":null} evidence: {"rule":"D-OWNER","owner_pac":"2668900119","source_pk":264297,"type_owner":"O","enrollment_id":"O20250108002715","role_code_owner":"72","role_text_owner":"ADP OF THE SNF","dst_resolved_via":"pecos_enrlmt_id","percentage_ownership_raw":null,"enrollment_organization_name":"BH CHESHIRE LLC"} |
| owns → | BH WEST RIVER LLC (CT) | 1.000 | snf_all_owners | evidencerecorded: 2026-06-16 methodology: entity-graph/v1 attributes: {"role_code":"72","association_date":"01/23/2025","percentage_ownership":null} evidence: {"rule":"D-OWNER","owner_pac":"2668900119","source_pk":264369,"type_owner":"O","enrollment_id":"O20250109001624","role_code_owner":"72","role_text_owner":"ADP OF THE SNF","dst_resolved_via":"pecos_enrlmt_id","percentage_ownership_raw":null,"enrollment_organization_name":"BH WEST RIVER LLC"} |
| owns → | BH LONG RIDGE LLC (CT) | 1.000 | snf_all_owners | evidencerecorded: 2026-06-16 methodology: entity-graph/v1 attributes: {"role_code":"72","association_date":"01/10/2025","percentage_ownership":null} evidence: {"rule":"D-OWNER","owner_pac":"2668900119","source_pk":264423,"type_owner":"O","enrollment_id":"O20250110002169","role_code_owner":"72","role_text_owner":"ADP OF THE SNF","dst_resolved_via":"pecos_enrlmt_id","percentage_ownership_raw":null,"enrollment_organization_name":"BH LONG RIDGE LLC"} |
| owns → | BH MILFORD LLC (CT) | 1.000 | snf_all_owners | evidencerecorded: 2026-06-16 methodology: entity-graph/v1 attributes: {"role_code":"72","association_date":"10/01/2024","percentage_ownership":null} evidence: {"rule":"D-OWNER","owner_pac":"2668900119","source_pk":265378,"type_owner":"O","enrollment_id":"O20250130000885","role_code_owner":"72","role_text_owner":"ADP OF THE SNF","dst_resolved_via":"pecos_enrlmt_id","percentage_ownership_raw":null,"enrollment_organization_name":"BH MILFORD LLC"} |
| owns → | BH NEWINGTON LLC (CT) | 1.000 | snf_all_owners | evidencerecorded: 2026-06-16 methodology: entity-graph/v1 attributes: {"role_code":"72","association_date":"10/01/2024","percentage_ownership":null} evidence: {"rule":"D-OWNER","owner_pac":"2668900119","source_pk":265402,"type_owner":"O","enrollment_id":"O20250130002307","role_code_owner":"72","role_text_owner":"ADP OF THE SNF","dst_resolved_via":"pecos_enrlmt_id","percentage_ownership_raw":null,"enrollment_organization_name":"BH NEWINGTON LLC"} |
| owns → | BH DANBURY LLC (CT) | 1.000 | snf_all_owners | evidencerecorded: 2026-06-16 methodology: entity-graph/v1 attributes: {"role_code":"72","association_date":"10/01/2024","percentage_ownership":null} evidence: {"rule":"D-OWNER","owner_pac":"2668900119","source_pk":265434,"type_owner":"O","enrollment_id":"O20250130003138","role_code_owner":"72","role_text_owner":"ADP OF THE SNF","dst_resolved_via":"pecos_enrlmt_id","percentage_ownership_raw":null,"enrollment_organization_name":"BH DANBURY 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=…