Triple
T21013305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EMS |
E517606
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Healthcare provider |
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 Context triple: [EMS, instanceOf, Healthcare provider]
-
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 entrepreneur
A healthcare entrepreneur is an individual who identifies unmet medical or wellness needs and builds innovative, sustainable ventures—often leveraging technology, services, or new care models—to improve health outcomes and patient experiences.
-
D.
healthcare technology company
A healthcare technology company develops and delivers digital tools, platforms, and data-driven solutions that improve the efficiency, quality, and accessibility of medical care and health management.
-
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_69e0b50192308190a284fcc89dd23a49 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 1:54 p.m.