Triple
T15702568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEC men's basketball regular season |
E380629
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | college basketball regular season |
C30344
|
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 regular season Context triple: [SEC men's basketball regular season, instanceOf, college basketball regular season]
-
A.
college basketball season
chosen
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.
-
B.
college basketball conference regular season title
A college basketball conference regular season title is the championship awarded to the team with the best performance in conference games over the course of the regular season schedule.
-
C.
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.
-
D.
college basketball student section
A college basketball student section is the designated area in an arena where enrolled students gather to loudly support their team with coordinated chants, cheers, and traditions during games.
-
E.
college basketball rivalry
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.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:45 a.m.