Triple
T26244560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulations for University Offices |
E656406
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cambridge University regulation |
C50391
|
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: Cambridge University regulation Context triple: [Regulations for University Offices, instanceOf, Cambridge University regulation]
-
A.
school of the University of Cambridge
A school of the University of Cambridge is an administrative grouping of related faculties and departments that coordinates academic strategy, governance, and resource allocation within a broad disciplinary area of the university.
-
B.
office within the University of Cambridge
chosen
An office within the University of Cambridge is an administrative or academic workspace assigned to staff or faculty for conducting university-related duties, meetings, and research activities.
-
C.
college of the University of Cambridge
A college of the University of Cambridge is a self-governing constituent institution that provides residential, social, and academic support to its members within the wider framework of the university.
-
D.
Cambridge don
A Cambridge don is a senior academic at the University of Cambridge, typically a fellow of a college, responsible for teaching, research, and often pastoral care of students.
-
E.
University of Cambridge award
A University of Cambridge award is a formal recognition, prize, or honor conferred by the University of Cambridge to acknowledge outstanding academic, research, or service achievements by individuals or groups associated with the institution.
- 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_69ee5b4c59a881909d9ee4fd013fffd5 |
completed | April 26, 2026, 6:37 p.m. |
Created at: April 26, 2026, 9:05 p.m.