Skip to content
FonteumPublic-records evidence

TERMINAL · ENTITY CARD · PERSON

WENDY SEKEL

Canonical entity in the resolved graph · methodology entity-graph/v1 · 57e74b61-694f-4791-8100-119d30225fb9

active

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.

Current identifier attachments with link confidence
SchemeValueSource tableLink methodConfidenceSinceProvenance
pac_id5698028272snf_all_ownersdeterministic_pac_in_all_owners1.0002026-06-14
evidence
recorded: 2026-06-14
methodology: entity-graph/v1
evidence: {"rule":"D-OWNER","source_pk":111426,"type_owner":"I","enrollment_id":"O20120110000475"}

Graph edges

One-hop relationships — ownership, chain membership, operation — each backed by a federal source row.

Current 1-hop graph edges
RelationshipEntityConfidenceSource tableProvenance
owns →WELLTOWER OPCO GROUP LLC (OH)1.000snf_all_owners
evidence
recorded: 2026-06-14
methodology: entity-graph/v1
attributes: {"role_code":"43","association_date":"11/01/2018","percentage_ownership":null}
evidence: {"rule":"D-OWNER","owner_pac":"5698028272","source_pk":187908,"type_owner":"I","enrollment_id":"O20190218001814","role_code_owner":"43","role_text_owner":"OPERATIONAL/MANAGERIAL CONTROL","dst_resolved_via":"pac_id","percentage_ownership_raw":null,"enrollment_organization_name":"WELLTOWER OPCO GROUP LLC"}
owns →MAPLEWOOD PARK RETIREMENT SERVICES INC (MD)1.000snf_all_owners
evidence
recorded: 2026-06-16
methodology: entity-graph/v1
attributes: {"role_code":"43","association_date":"08/30/2017","percentage_ownership":0}
evidence: {"rule":"D-OWNER","owner_pac":"5698028272","source_pk":111426,"type_owner":"I","enrollment_id":"O20120110000475","role_code_owner":"43","role_text_owner":"OPERATIONAL/MANAGERIAL CONTROL","dst_resolved_via":"pecos_enrlmt_id","percentage_ownership_raw":0,"enrollment_organization_name":"MAPLEWOOD PARK RETIREMENT SERVICES INC"}
owns →WELLTOWER OPCO GROUP LLC (VA)1.000snf_all_owners
evidence
recorded: 2026-06-16
methodology: entity-graph/v1
attributes: {"role_code":"43","association_date":"01/16/2025","percentage_ownership":null}
evidence: {"rule":"D-OWNER","owner_pac":"5698028272","source_pk":184732,"type_owner":"I","enrollment_id":"O20181029001871","role_code_owner":"43","role_text_owner":"OPERATIONAL/MANAGERIAL CONTROL","dst_resolved_via":"pecos_enrlmt_id","percentage_ownership_raw":null,"enrollment_organization_name":"WELLTOWER OPCO GROUP LLC"}
owns →WELLTOWER CCRC OPCO LLC (MD)1.000snf_all_owners
evidence
recorded: 2026-06-16
methodology: entity-graph/v1
attributes: {"role_code":"43","association_date":"08/23/2022","percentage_ownership":null}
evidence: {"rule":"D-OWNER","owner_pac":"5698028272","source_pk":185202,"type_owner":"I","enrollment_id":"O20181102001066","role_code_owner":"43","role_text_owner":"OPERATIONAL/MANAGERIAL CONTROL","dst_resolved_via":"pecos_enrlmt_id","percentage_ownership_raw":null,"enrollment_organization_name":"WELLTOWER CCRC OPCO LLC"}
owns →WELLTOWER CCRC OPCO LLC (VA)1.000snf_all_owners
evidence
recorded: 2026-06-16
methodology: entity-graph/v1
attributes: {"role_code":"43","association_date":"08/23/2022","percentage_ownership":null}
evidence: {"rule":"D-OWNER","owner_pac":"5698028272","source_pk":186178,"type_owner":"I","enrollment_id":"O20181206000405","role_code_owner":"43","role_text_owner":"OPERATIONAL/MANAGERIAL CONTROL","dst_resolved_via":"pecos_enrlmt_id","percentage_ownership_raw":null,"enrollment_organization_name":"WELLTOWER CCRC OPCO LLC"}
owns →WELLTOWER OPCO GROUP LLC (FL)1.000snf_all_owners
evidence
recorded: 2026-06-16
methodology: entity-graph/v1
attributes: {"role_code":"43","association_date":"11/01/2018","percentage_ownership":null}
evidence: {"rule":"D-OWNER","owner_pac":"5698028272","source_pk":187908,"type_owner":"I","enrollment_id":"O20190218001814","role_code_owner":"43","role_text_owner":"OPERATIONAL/MANAGERIAL CONTROL","dst_resolved_via":"pecos_enrlmt_id","percentage_ownership_raw":null,"enrollment_organization_name":"WELLTOWER OPCO GROUP LLC"}
owns →WELLTOWER OPCO GROUP LLC (NJ)1.000snf_all_owners
evidence
recorded: 2026-06-16
methodology: entity-graph/v1
attributes: {"role_code":"43","association_date":"12/15/2017","percentage_ownership":null}
evidence: {"rule":"D-OWNER","owner_pac":"5698028272","source_pk":203271,"type_owner":"I","enrollment_id":"O20200818000802","role_code_owner":"43","role_text_owner":"OPERATIONAL/MANAGERIAL CONTROL","dst_resolved_via":"pecos_enrlmt_id","percentage_ownership_raw":null,"enrollment_organization_name":"WELLTOWER OPCO GROUP LLC"}
owns →SH OPCO THE QUADRANGLE LLC (PA)1.000snf_all_owners
evidence
recorded: 2026-06-16
methodology: entity-graph/v1
attributes: {"role_code":"43","association_date":"01/16/2025","percentage_ownership":0}
evidence: {"rule":"D-OWNER","owner_pac":"5698028272","source_pk":205383,"type_owner":"I","enrollment_id":"O20201120001225","role_code_owner":"43","role_text_owner":"OPERATIONAL/MANAGERIAL CONTROL","dst_resolved_via":"pecos_enrlmt_id","percentage_ownership_raw":0,"enrollment_organization_name":"SH OPCO THE QUADRANGLE LLC"}
owns →SH OPCO THE FAIRFAX LLC (VA)1.000snf_all_owners
evidence
recorded: 2026-06-16
methodology: entity-graph/v1
attributes: {"role_code":"43","association_date":"01/16/2025","percentage_ownership":0}
evidence: {"rule":"D-OWNER","owner_pac":"5698028272","source_pk":206279,"type_owner":"I","enrollment_id":"O20201222002489","role_code_owner":"43","role_text_owner":"OPERATIONAL/MANAGERIAL CONTROL","dst_resolved_via":"pecos_enrlmt_id","percentage_ownership_raw":0,"enrollment_organization_name":"SH OPCO THE FAIRFAX 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.

As of
Diff

Pick a date to reconstruct, or two dates to diff. Equivalent JSON: /api/v1/history/{subject_type}/{subject_id}?at=… and …/diff?from=…&to=…

Request access