Triple
T25433618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federally Qualified Health Centers |
E637320
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | healthcare provider designation |
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: healthcare provider designation Context triple: [Federally Qualified Health Centers, instanceOf, healthcare provider designation]
-
A.
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.
-
B.
clinical care provider
A clinical care provider is a trained healthcare professional who assesses, diagnoses, treats, and manages patients’ health needs in clinical settings.
-
C.
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.
-
D.
healthcare administration service
A healthcare administration service manages the non-clinical operations of healthcare organizations, including scheduling, billing, compliance, records management, and coordination among providers, payers, and patients to ensure efficient and compliant delivery of care.
-
E.
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.
- 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.