Triple
T1013730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIT researchers |
E21883
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | academic personnel |
C1010
|
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 personnel Context triple: [MIT researchers, instanceOf, academic personnel]
-
A.
university faculty
chosen
A university faculty is a group of academic staff and scholars within a higher education institution responsible for teaching, research, and academic governance in specific disciplines or departments.
-
B.
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.
-
C.
academic chair
An academic chair is a senior faculty position, often endowed, that provides leadership in a specific discipline through teaching, research, and service within a higher education institution.
-
D.
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.
-
E.
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.
- 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:41 p.m.