Triple
T9553850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McGill University Health Sciences sector |
E230491
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | academic health sciences ecosystem |
C16785
|
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: academic health sciences ecosystem Context triple: [McGill University Health Sciences sector, instanceOf, academic health sciences ecosystem]
-
A.
academic health care system
An academic health care system is an integrated organization that combines patient care, medical education, and research, typically centered around a teaching hospital affiliated with a medical school or university.
-
B.
academic health sciences center
chosen
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.
-
C.
public academic health center
A public academic health center is a publicly funded medical institution that integrates patient care, health professions education, and biomedical research, typically affiliated with a university.
-
D.
medical campus
A medical campus is a dedicated complex that integrates healthcare facilities, educational institutions, research centers, and support services within a unified environment focused on medical care and advancement.
-
E.
health sciences college
A health sciences college is an educational institution that offers specialized programs and training in fields related to healthcare, medicine, and allied health professions.
- 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_69ca847d3be8819099c9dad2a7e786f1 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:02 p.m.