Triple
T23419993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Choke |
E560624
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Houston Oilers historical event |
C1928
|
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 historical event Context triple: [The Choke, instanceOf, Houston Oilers historical event]
-
A.
National Football League history event
chosen
A National Football League history event is a significant occurrence or milestone—such as a game, rule change, record, or organizational decision—that has contributed to shaping the evolution and legacy of the NFL over time.
-
B.
Philadelphia 76ers history event
A Philadelphia 76ers history event is a significant occurrence or milestone related to the franchise’s development, achievements, personnel changes, or cultural impact across its existence in professional basketball.
-
C.
historical sports moment
A historical sports moment is a significant event or achievement in athletic competition that becomes widely remembered for its impact, drama, or cultural importance.
-
D.
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.
-
E.
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.
- 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 5:44 p.m.