Triple
T26085547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NightingaleHospitals |
E657968
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | temporary hospital network |
C51092
|
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: temporary hospital network Context triple: [NightingaleHospitals, instanceOf, temporary hospital network]
-
A.
public hospital network
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
temporary city
A temporary city is a short-lived, purpose-built urban environment that provides essential infrastructure, services, and social spaces for a limited time before being dismantled or abandoned.
- F. None of above. chosen
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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
Created at: April 26, 2026, 7:42 p.m.