Triple
T3048784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vice-Chancellor |
E83517
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university leadership position |
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 leadership position Context triple: [Vice-Chancellor, instanceOf, university leadership position]
-
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.
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.
-
C.
executive position
An executive position is a high-level organizational role responsible for setting strategic direction, making major decisions, and overseeing the performance and operations of a company or its key divisions.
-
D.
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.
-
E.
public administration position
A public administration position is a role within government or public sector organizations responsible for planning, implementing, and managing policies and services that serve the public interest.
- 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_69ad8b24924c8190a9bb6f61d519e4ae |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:01 p.m.