Triple
T22969861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University Hospital Wishaw |
E571154
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | acute district general 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: acute district general hospital Context triple: [University Hospital Wishaw, instanceOf, acute district general hospital]
-
A.
medical district
A medical district is a designated urban area where healthcare facilities, such as hospitals, clinics, research centers, and related services, are concentrated to provide comprehensive medical care and support.
-
B.
hospital
chosen
A hospital is a healthcare facility where medical professionals diagnose, treat, and care for patients using specialized equipment and services.
-
C.
teaching hospital
A teaching hospital is a medical facility that provides patient care while simultaneously serving as a training and research center for medical students, residents, and other healthcare professionals, typically in affiliation with a medical school.
-
D.
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.
-
E.
academic medical center unit
An academic medical center unit is a specialized organizational subdivision within a teaching hospital or academic health system that integrates patient care, medical education, and research in a specific clinical or administrative domain.
- 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_69e245b2c6548190a0e4c7f2f7df2d48 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:48 p.m.