Triple
T19197010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle for the Bluegrass |
E469997
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | college basketball rivalry game |
C21136
|
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 game Context triple: [Battle for the Bluegrass, instanceOf, college basketball rivalry game]
-
A.
college basketball rivalry
chosen
A college basketball rivalry is a recurring, highly competitive series of games between two collegiate teams characterized by historical significance, regional or conference proximity, and intense fan and media interest.
-
B.
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.
-
C.
college basketball season
A college basketball season is the annual cycle of organized practices, regular-season games, conference tournaments, and postseason play in which collegiate teams compete to determine rankings, championships, and player development outcomes.
-
D.
college baseball rivalry game
A college baseball rivalry game is a highly anticipated, emotionally charged matchup between two collegiate teams with a long-standing competitive history, often drawing large crowds and heightened media attention.
-
E.
college basketball television program
A college basketball television program is a broadcast show that provides live or recorded coverage, analysis, and commentary on collegiate basketball games, teams, and related news.
- 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_69d8dd0ad9088190a173b32657ae2e7a |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:07 p.m.