Triple
T1785423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big 5 basketball |
E39380
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | college basketball rivalry association |
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 basketball rivalry association Context triple: [Big 5 basketball, instanceOf, college basketball rivalry association]
-
A.
college basketball tournament
A college basketball tournament is a structured, multi-game competition in which collegiate teams compete in a bracketed or round-robin format to determine a champion.
-
B.
continental basketball confederation
A continental basketball confederation is a regional governing body responsible for organizing, regulating, and promoting basketball competitions and development across multiple national federations within a specific continent.
-
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 basketball award program
A college basketball award program is a structured system that recognizes and honors players, coaches, and teams for outstanding performance, sportsmanship, and achievements throughout a season or tournament.
-
E.
NCAA Division I basketball team
An NCAA Division I basketball team is a collegiate basketball program that competes at the highest level of National Collegiate Athletic Association competition, adhering to specific scholarship, eligibility, and scheduling requirements.
- 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_69a88630519c8190a17addd83c4a3ef4 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:31 p.m.