Triple
T3631979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Region XV of the NJCAA |
E76976
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collegiate athletic 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: collegiate athletic organization Context triple: [Region XV of the NJCAA, instanceOf, collegiate athletic organization]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
collegiate athletics governance subdivision
A collegiate athletics governance subdivision is an organizational tier within a larger college sports governing body that sets and enforces rules, policies, and competitive structures for a defined group of member institutions.
-
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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:23 p.m.