Triple
T37870116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Master of Pembroke College, Cambridge |
E944581
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | governing role in a Cambridge college |
C65765
|
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: governing role in a Cambridge college Context triple: [Master of Pembroke College, Cambridge, instanceOf, governing role in a Cambridge college]
-
A.
office within the University of Cambridge
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.
-
B.
position at Gonville and Caius College
A "position at Gonville and Caius College" represents a specific academic, administrative, or fellowship role formally held by an individual within Gonville and Caius College, Cambridge.
-
C.
faculty within a royal college
The faculty within a royal college is the collective body of academic and professional staff responsible for teaching, research, and governance under the auspices of a monarch-chartered institution.
-
D.
University of Cambridge term
A University of Cambridge term is a formally defined academic period during which teaching, examinations, and official university activities take place.
-
E.
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.
- F. None of above. chosen
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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.