Triple
T28462091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York City Health + Hospitals |
E720181
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipal hospital system |
C26598
|
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: municipal hospital system Context triple: [New York City Health + Hospitals, instanceOf, municipal hospital system]
-
A.
regional hospital system
A regional hospital system is an organized network of hospitals and related healthcare facilities within a specific geographic area that coordinates services, resources, and administration to provide comprehensive medical care to the local population.
-
B.
hospital system facilities
A hospital system facilities class represents the physical infrastructure, equipment, and support services that enable the delivery of healthcare across one or more hospital locations.
-
C.
public hospital network
chosen
A public hospital network is a coordinated system of government-funded hospitals and healthcare facilities that collaboratively provide accessible, often low-cost or free, medical services to a defined population or region.
-
D.
medical system
A medical system is an organized framework of people, institutions, technologies, and processes that work together to deliver healthcare services for maintaining and improving individuals’ health.
-
E.
state-operated healthcare facility
A state-operated healthcare facility is a medical institution owned, funded, and managed by a government entity to provide health services to the public, often emphasizing accessibility and public health priorities.
- 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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 2:41 a.m.