Triple
T26053957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1980 Dallas Cowboys season |
E648062
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Dallas Cowboys season |
C50185
|
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: Dallas Cowboys season Context triple: [1980 Dallas Cowboys season, instanceOf, Dallas Cowboys season]
-
A.
Dallas Cowboys facility
A Dallas Cowboys facility is a specialized sports complex that houses the team's training, administrative, medical, and operational functions, including practice fields, offices, meeting rooms, and support amenities.
-
B.
Dallas Cowboys award recipient
A Dallas Cowboys award recipient is an individual recognized by the Dallas Cowboys organization for outstanding performance, contribution, or achievement related to the team.
-
C.
Chicago Bears season
A Chicago Bears season is a yearly period in which the Chicago Bears NFL team competes in regular-season and, if qualified, postseason games, encompassing their performance, roster, statistics, and notable events for that year.
-
D.
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.
-
E.
Minnesota Vikings season
A Minnesota Vikings season represents a single year of the franchise’s participation in the National Football League, encompassing all preseason, regular season, and postseason games, team performance, roster changes, and notable events for that year.
- 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_69e77e8d419481908004e6318d28aaab |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 9:11 a.m.