Triple
T2856881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Steward of the University of Cambridge |
E63221
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university office |
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 office Context triple: [High Steward of the University of Cambridge, instanceOf, university office]
-
A.
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.
-
B.
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.
-
C.
university
A university is an institution of higher education and research that grants academic degrees and fosters advanced learning across diverse fields of study.
-
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.
private university
A private university is a higher education institution that is independently funded and operated, primarily through tuition, donations, and endowments rather than direct government support.
- 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_69ab4c41e8c08190a9e8f5249cc12610 |
completed | March 6, 2026, 9:50 p.m. |
Created at: March 6, 2026, 10:02 p.m.