Triple
T19902658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Association BAME Officer |
E478330
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Students’ Association officer role |
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: Students’ Association officer role Context triple: [Association BAME Officer, instanceOf, Students’ Association officer role]
-
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.
student life organization
A student life organization is a campus-based group that plans and supports activities, services, and programs to enhance students’ social, cultural, and personal development outside the classroom.
-
C.
undergraduate student organization
An undergraduate student organization is a formally recognized group of college students who collaborate around shared interests, goals, or identities to provide activities, support, and community within the university.
-
D.
student-life leadership office
The student-life leadership office is a campus unit that develops, supports, and coordinates programs, resources, and advising to foster student leadership, engagement, and community involvement.
-
E.
education ministerial role
An education ministerial role is a government position responsible for developing, implementing, and overseeing national policies, standards, and programs related to education systems and institutions.
- 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:52 p.m.