Triple
T5398996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chancellor of the University of Sussex |
E120728
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university chancellor role |
C53
|
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 chancellor role Context triple: [Chancellor of the University of Sussex, instanceOf, university chancellor role]
-
A.
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.
-
B.
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.
-
C.
academic administrator
chosen
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.
-
D.
university faculty
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.
-
E.
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.
- 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_69bd4637b92c8190b815b6443ae4b323 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:04 p.m.