Triple
T25173320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University Health Network |
E630379
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research hospital organization |
C49841
|
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: research hospital organization Context triple: [University Health Network, instanceOf, research hospital organization]
-
A.
research organization
A research organization is an institution that systematically investigates specific questions or problems to generate new knowledge, technologies, or insights, often within scientific, academic, or applied domains.
-
B.
medical organization
A medical organization is an entity that coordinates healthcare services, resources, and professionals to promote, maintain, or restore people’s health.
-
C.
health systems research organisation
A health systems research organisation is an entity that systematically studies how health services are organized, financed, delivered, and governed to generate evidence that improves the performance, equity, and resilience of health systems.
-
D.
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.
-
E.
academic health sciences center
An academic health sciences center is an integrated institution that combines clinical care, health professions education, and biomedical research, typically linking a medical school with one or more teaching hospitals and related health programs.
- 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_69e75a87c9b88190ab60731902a99750 |
completed | April 21, 2026, 11:07 a.m. |
Created at: April 21, 2026, 12:21 p.m.