Triple
T4946738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red River Showdown |
E111068
|
entity |
| Predicate | seriesIncludesPostseasonGames |
P60107
|
FINISHED |
| Object | false |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: false | Statement: [Red River Showdown, seriesIncludesPostseasonGames, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesIncludesPostseasonGames Context triple: [Red River Showdown, seriesIncludesPostseasonGames, false]
-
A.
includesPostseasonIn
Indicates that a time period, schedule, or dataset explicitly encompasses postseason games or events in addition to the regular season.
-
B.
isPostseasonGame
Indicates that the game takes place during a postseason or playoff phase rather than the regular season.
-
C.
hasPostseasonEvent
Indicates that an entity is associated with or participates in a postseason event, such as playoffs or championships, following a regular season.
-
D.
postseasonGamesPlayed
Indicates the number of games an entity has participated in during postseason or playoff competition.
-
E.
hasPostseasonAccess
Indicates that an entity is granted the right or eligibility to participate in postseason or playoff competitions.
- F. None of above. chosen
Provenance (4 batches)
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_69bd441721cc819085c7e33fe0876818 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd70abf8dc819090269d0e1ce9f871 |
completed | March 20, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3aa1388190b3e0c8ee1ba1e4fa |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6fa2d2088190ae444d3d0e47d5d2 |
completed | March 20, 2026, 4:02 p.m. |
Created at: March 20, 2026, 1:31 p.m.