Triple
T25433671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federally Qualified Health Center look-alikes |
E637321
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | safety net provider category |
C31723
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: safety net provider category Context triple: [Federally Qualified Health Center look-alikes, instanceOf, safety net provider category]
-
A.
healthcare provider network
A healthcare provider network is an organized group of doctors, hospitals, and other medical professionals and facilities that contract with a health plan to deliver coordinated care to its members.
-
B.
health insurance provider
A health insurance provider is an organization that offers and manages health coverage plans, collecting premiums and paying for or reimbursing members’ eligible medical expenses according to policy terms.
-
C.
healthcare services provider
chosen
A healthcare services provider is an organization or individual that delivers medical, therapeutic, or preventive health services to patients to diagnose, treat, and manage health conditions.
-
D.
welfare facility network
A welfare facility network is an interconnected system of organizations and service centers that collaboratively provide social support, care, and resources to individuals and communities in need.
-
E.
benefits administration provider
A benefits administration provider is an organization that manages and streamlines employee benefits programs—such as health insurance, retirement plans, and other perks—on behalf of employers to ensure accurate enrollment, compliance, and ongoing support.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 1:59 p.m.