Triple
T5764372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Academic Senate of the University of Bologna |
E127173
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collegial governing body |
C14139
|
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: collegial governing body Context triple: [Academic Senate of the University of Bologna, instanceOf, collegial governing body]
-
A.
collegiate body
chosen
A collegiate body is a formal group of individuals who collectively deliberate, decide, or govern on matters within a shared institutional or organizational authority.
-
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.
collegial government
A collegial government is a form of governance in which executive authority is shared among a group of individuals who collectively deliberate and decide on public policy, rather than being vested in a single leader.
-
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.
student representative body
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.
- 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_69c00833a3fc81908f4bc29ed011b7a6 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:49 p.m.