Triple
T5478494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yale University Council of Deans |
E123413
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | academic leadership body |
C1666
|
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 leadership body Context triple: [Yale University Council of Deans, instanceOf, academic leadership body]
-
A.
academic leadership office
An academic leadership office is a centralized unit within an educational institution responsible for guiding strategic direction, supporting faculty and program development, and coordinating policies and initiatives that advance the institution’s academic mission.
-
B.
senior leadership body
chosen
A senior leadership body is a group of high-level executives or officials responsible for setting strategic direction, making key organizational decisions, and overseeing overall performance and governance.
-
C.
academic association
An academic association is an organized group of scholars, researchers, and professionals dedicated to advancing knowledge, collaboration, and standards within a specific academic discipline or field.
-
D.
university governing body
A university governing body is a formal group of appointed or elected individuals responsible for setting the institution’s strategic direction, overseeing its policies and finances, and ensuring accountability and compliance with legal and educational standards.
-
E.
academic administrator
An academic administrator is a professional responsible for planning, organizing, and overseeing the non-teaching operations and policies of educational institutions to support their academic mission.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:09 p.m.