Triple
T2251271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Bowl XXVI |
E49620
|
entity |
| Predicate | BillsRecordEnteringGame |
P36723
|
FINISHED |
| Object | 13–3 |
—
|
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: 13–3 | Statement: [Super Bowl XXVI, BillsRecordEnteringGame, 13–3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BillsRecordEnteringGame Context triple: [Super Bowl XXVI, BillsRecordEnteringGame, 13–3]
-
A.
NFCChampionRecordEnteringGame
Indicates the NFC team's season record at the time they enter a particular game, reflecting their performance up to but not including that game.
-
B.
EaglesRecordEnteringGame
Indicates the statistical record or performance status of the Eagles team as it stood immediately before a specific game began.
-
C.
BroncosRecordEnteringGame
Indicates the win-loss record that the Broncos team had prior to the start of a specific game.
-
D.
ChiefsRecordEnteringGame
Indicates the win-loss (and possibly tie) record the Chiefs had prior to the start of a specific game.
-
E.
PatriotsRecordEnteringGame
Indicates the win-loss (and possibly tie) record the Patriots had prior to the start of a specific game.
- 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_69a88aaa9250819095e127d0d77e8a32 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc11d04688190abc04fac3a1804a9 |
completed | March 7, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69abbdb34c148190b51e99f540f97204 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbe86dbcc81908c72793af8fe2a4d |
completed | March 7, 2026, 5:58 a.m. |
Created at: March 4, 2026, 7:47 p.m.