Triple
T5770675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yale University administration |
E127323
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university administration |
C1500
|
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: university administration Context triple: [Yale University administration, instanceOf, university administration]
-
A.
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.
-
B.
university administrative unit
chosen
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.
-
C.
academic administrative office
An academic administrative office is a centralized unit within an educational institution responsible for managing academic records, coordinating course and program logistics, supporting faculty and students with administrative processes, and ensuring compliance with institutional and regulatory policies.
-
D.
university
A university is an institution of higher education and research that grants academic degrees and fosters advanced learning across diverse fields of study.
-
E.
university system
A university system is an integrated organizational framework that manages academic programs, students, faculty, resources, and administrative processes across one or more higher education institutions.
- 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:50 p.m.