Triple
T9142606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Graduate Student Assembly |
E219366
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | student government organization |
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 government organization Context triple: [Graduate Student Assembly, instanceOf, student government organization]
-
A.
student-led organization
A student-led organization is a group formed and managed primarily by students to pursue shared interests, goals, or activities within or beyond an educational institution.
-
B.
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.
-
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 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.
-
E.
national student organization
A national student organization is a formally structured, student-led group that operates across multiple educational institutions within a country to represent student interests, coordinate activities, and provide shared resources and opportunities.
- 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_69ca83e012288190a5771058adbaabd2 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:19 p.m.