Triple
T3094461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chancellor of the University of the Western Cape |
E64559
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university ceremonial office |
C2527
|
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 ceremonial office Context triple: [Chancellor of the University of the Western Cape, instanceOf, university ceremonial office]
-
A.
ceremonial office
chosen
A ceremonial office is a formal position or title that carries symbolic, traditional, or representative duties rather than substantive executive or administrative power.
-
B.
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.
-
C.
ceremonial officer
A ceremonial officer is an individual responsible for organizing, overseeing, and performing formal duties and rituals at official events, ceremonies, and public functions.
-
D.
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.
-
E.
university administrative unit
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.
- 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_69ad857c97d88190b26f9b1c90839c77 |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:03 p.m.