Triple
T36591466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ONEFA |
E902680
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | college athletics organization |
C191
|
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: college athletics organization Context triple: [ONEFA, instanceOf, college athletics organization]
-
A.
college athletics governing body
A college athletics governing body is an organization that creates, enforces, and oversees rules, eligibility standards, and competition structures for intercollegiate sports programs.
-
B.
college football organization
A college football organization is an entity that governs, coordinates, and promotes intercollegiate football programs, overseeing competition rules, scheduling, eligibility, and related administrative and developmental activities.
-
C.
collegiate athletic conference
chosen
A collegiate athletic conference is an organized group of colleges and universities that compete against each other in intercollegiate sports under shared rules, governance, and scheduling agreements.
-
D.
college athletics conference office
A college athletics conference office is the central administrative organization that governs, coordinates, and supports athletic competition, compliance, scheduling, and shared initiatives among its member colleges and universities.
-
E.
college athletic program
A college athletic program is an organized set of sports teams, resources, and support services sponsored by a college or university to provide competitive and recreational athletic opportunities for its students.
- 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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.