Triple
T2291613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Bowl VII |
E51515
|
entity |
| Predicate | RedskinsRegularSeasonRecord |
P36389
|
FINISHED |
| Object | 11–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: 11–3 | Statement: [Super Bowl VII, RedskinsRegularSeasonRecord, 11–3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RedskinsRegularSeasonRecord Context triple: [Super Bowl VII, RedskinsRegularSeasonRecord, 11–3]
-
A.
RedskinsRecordRegularSeason
chosen
Indicates the win-loss-tie record achieved by the Washington Redskins during a specific NFL regular season.
-
B.
RedskinsRecordEnteringGame
Indicates the win-loss (and possibly tie) record that the Redskins team had prior to the start of a specific game.
-
C.
EaglesRegularSeasonRecord
Indicates the win-loss (and possibly tie) performance of the Eagles during a specific regular season.
-
D.
RedskinsFranchiseSuperBowlLossesAfterGame
Indicates that the Washington Redskins franchise had a Super Bowl loss occurring after a specified game.
-
E.
RedskinsPointsByQuarter
Indicates the number of points the Redskins scored in each quarter of a game.
- F. None of above.
Provenance (3 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_69a88b09c644819090b503456d96bf70 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abcd0e42248190ada33b84d75caa64 |
completed | March 7, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69abc589295c819092989820c2b4e9d8 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:48 p.m.