Triple
T23420192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1979 Houston Oilers season |
E560629
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Houston Oilers season |
C47657
|
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: Houston Oilers season Context triple: [1979 Houston Oilers season, instanceOf, Houston Oilers season]
-
A.
Kansas City Chiefs season
A Kansas City Chiefs season represents a single year of the franchise’s professional football activities, encompassing all preseason, regular season, and postseason games, player and staff changes, and team performance outcomes.
-
B.
Los Angeles Lakers season
A Los Angeles Lakers season is the annual campaign in which the Lakers basketball team competes in the NBA’s regular season and playoffs, encompassing all games, player performances, transactions, and organizational events for that year.
-
C.
Sacramento Kings season
The "Sacramento Kings season" conceptual class represents a single NBA campaign for the Sacramento Kings, encompassing the team's roster, schedule, game results, player and team statistics, transactions, standings, and postseason performance for that specific year.
-
D.
XFL team
An XFL team is a professional American football franchise that competes in the XFL league, representing a specific city or region with its own roster, branding, and fan base.
-
E.
American Football League season
An American Football League season is the annual schedule of professional gridiron football games, standings, and playoffs contested by AFL teams culminating in the league championship.
- 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 5:44 p.m.