Triple
T22373454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convocation of the University of Oxford |
E553098
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university assembly |
C36413
|
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 assembly Context triple: [Convocation of the University of Oxford, instanceOf, university assembly]
-
A.
university association
A university association is an organized group within a higher education institution that brings together students, staff, or alumni around shared academic, professional, cultural, or social interests to provide support, activities, and representation.
-
B.
scholarly assembly
chosen
A scholarly assembly is a formal gathering of academics and experts convened to present, discuss, and critique research, ideas, and findings within a specific field or across disciplines.
-
C.
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.
-
D.
university ceremonial venue
A university ceremonial venue is a formal campus space designed and equipped to host official academic events such as graduations, inaugurations, convocations, and other institutional ceremonies.
-
E.
campus
A campus is a defined area of land that houses the buildings, facilities, and open spaces of an educational institution, supporting academic, residential, and social activities.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:45 p.m.