Triple
T1844662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston University School of Medicine |
E41256
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | academic division of Boston University |
C57
|
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 division of Boston University Context triple: [Boston University School of Medicine, instanceOf, academic division of Boston University]
-
A.
academic division
chosen
An academic division is a major organizational unit within an educational institution that groups related departments, programs, or disciplines under a common administrative and academic structure.
-
B.
academic district
An academic district is a designated area within a city or region where educational institutions and related facilities are concentrated, fostering learning, research, and scholarly activities.
-
C.
university administrative unit
A university administrative unit is an organizational division within a university responsible for managing specific operational, academic, or support functions to ensure the institution runs effectively and complies with policies and regulations.
-
D.
college within a university
A college within a university is a semi-autonomous academic division that groups related disciplines, manages specific degree programs, and oversees faculty and resources within its subject area.
-
E.
college of the University of Toronto
A college of the University of Toronto is a semi-autonomous academic and social community within the university that provides students with residence options, advising, programming, and a distinct intellectual and cultural environment.
- 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:33 p.m.