Triple
T38079682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEC Western Division vs SEC Eastern Division |
E950817
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intra-conference matchup structure |
C66496
|
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: intra-conference matchup structure Context triple: [SEC Western Division vs SEC Eastern Division, instanceOf, intra-conference matchup structure]
-
A.
sports analytics conference
A sports analytics conference is a professional gathering where experts, practitioners, and enthusiasts share research, tools, and strategies for using data and statistical methods to improve performance, decision-making, and fan engagement in sports.
-
B.
sports playoff system
A sports playoff system is a structured, typically elimination-based competition format used at the end of a regular season to determine a league or tournament champion among qualifying teams.
-
C.
basketball competition system
A basketball competition system is a structured framework that organizes teams, schedules games, tracks results and statistics, and determines rankings and progression through leagues or tournaments.
-
D.
single-elimination tournament
A single-elimination tournament is a competition format in which participants are paired in matches and immediately removed from the tournament upon losing, continuing until only one undefeated winner remains.
-
E.
sports conference collective term
A sports conference collective term refers to the shared name or label used to group multiple athletic teams or schools that regularly compete against each other within an organized league or association.
- F. None of above. chosen
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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.