Triple
T27323034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emory Long-Term Acute Care Hospital |
E689560
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | long-term acute care hospital |
C94
|
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: long-term acute care hospital Context triple: [Emory Long-Term Acute Care Hospital, instanceOf, long-term acute care hospital]
-
A.
federal healthcare facility
A federal healthcare facility is a government-operated medical institution that provides healthcare services to eligible individuals, such as military personnel, veterans, and certain civilian populations, under federal authority and funding.
-
B.
private healthcare facility
A private healthcare facility is a non-governmental medical institution funded and operated by individuals or organizations to provide healthcare services, typically on a fee-for-service or insurance-reimbursed basis.
-
C.
long-term care insurance program
A long-term care insurance program is a financial protection plan that helps cover the costs of extended care services—such as nursing homes, assisted living, or in-home care—when individuals can no longer perform basic daily activities independently.
-
D.
tertiary care center
A tertiary care center is a specialized healthcare facility that provides advanced, highly specialized diagnostic, therapeutic, and surgical services typically unavailable at primary or secondary care institutions.
-
E.
hospital
chosen
A hospital is a healthcare facility where medical professionals diagnose, treat, and care for patients using specialized equipment and services.
- 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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
Created at: April 27, 2026, 11:34 a.m.