Triple
T30390822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Financial Management Association chapter |
E773078
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university student chapter |
C9976
|
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 student chapter Context triple: [Financial Management Association chapter, instanceOf, university student chapter]
-
A.
collegiate chapter
chosen
A collegiate chapter is a local, student-run branch of a larger national or international organization that operates within a college or university to advance the group’s mission through campus-based activities and membership.
-
B.
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.
-
C.
regional chapter network
A regional chapter network is a coordinated system of local chapters within a defined geographic area that collaborate under a shared mission, governance structure, and resource framework to advance common goals.
-
D.
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.
-
E.
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.
- 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_69f2248ef0a48190aa54d4d8ac3e5758 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:02 p.m.