Triple
T11588239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto General Hospital |
E274808
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tertiary care centre |
C21239
|
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: tertiary care centre Context triple: [Toronto General Hospital, instanceOf, tertiary care centre]
-
A.
tertiary care center
chosen
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.
-
B.
medical research centre
A medical research centre is an institution dedicated to conducting scientific studies and clinical investigations to advance knowledge, diagnosis, treatment, and prevention of diseases and health conditions.
-
C.
tertiary institution
A tertiary institution is an organization that provides post-secondary education and training, such as universities, colleges, and vocational schools, typically offering advanced academic and professional qualifications.
-
D.
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.
-
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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:38 p.m.