Triple
T7102171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Bowl XI |
E165483
|
entity |
| Predicate | RaidersRecordEnteringGame |
P74912
|
FINISHED |
| Object | 13–1 |
—
|
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–1 | Statement: [Super Bowl XI, RaidersRecordEnteringGame, 13–1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RaidersRecordEnteringGame Context triple: [Super Bowl XI, RaidersRecordEnteringGame, 13–1]
-
A.
ramsRecordEnteringGame
Indicates the performance record (such as wins and losses) that the Rams team holds at the time they enter a particular game.
-
B.
titansRecordEnteringGame
Indicates that the Titans team begins participation in a game, marking their official entry into the contest.
-
C.
RedskinsRecordEnteringGame
Indicates the win-loss (and possibly tie) record that the Redskins team had prior to the start of a specific game.
-
D.
VikingsRecordEnteringGame
Indicates the win-loss (and possibly tie) record the Vikings team holds immediately before a specific game is played.
-
E.
EaglesRecordEnteringGame
Indicates the statistical record or performance status of the Eagles team as it stood immediately before a specific game began.
- 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_69c6887fcddc8190a5d58908f6dee590 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e588aee08190bfb3d96135c0a322 |
completed | March 27, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a15b088190bee9a23e94aaac53 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:42 p.m.