Triple
T7663308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Student Representative Council (University of the Witwatersrand) |
E173560
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | student governance body |
C13722
|
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: student governance body Context triple: [Student Representative Council (University of the Witwatersrand), instanceOf, student governance body]
-
A.
student representative body
chosen
A student representative body is an organized group of students elected or selected to voice student interests, participate in institutional decision-making, and help shape policies and activities affecting the student community.
-
B.
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.
-
C.
student body
The student body is the collective group of all enrolled students within an educational institution, representing its primary learner population.
-
D.
governing body
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
E.
collegiate body
A collegiate body is a formal group of individuals who collectively deliberate, decide, or govern on matters within a shared institutional or organizational authority.
- 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_69c69955517c819085bc715b96d304d2 |
completed | March 27, 2026, 2:51 p.m. |
Created at: March 27, 2026, 3:59 p.m.