Triple
T435592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Bowl XLII |
E10003
|
entity |
| Predicate | decisiveTouchdownTimeRemaining |
P7561
|
FINISHED |
| Object | 0:35 |
—
|
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: 0:35 | Statement: [Super Bowl XLII, decisiveTouchdownTimeRemaining, 0:35]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisiveTouchdownTimeRemaining Context triple: [Super Bowl XLII, decisiveTouchdownTimeRemaining, 0:35]
-
A.
decidedInRegulationTime
Indicates that the outcome of a contest or match was determined within the standard allotted duration, without requiring any extra time or tiebreak procedures.
-
B.
halftimeScore
Indicates the score or result of a game or match at the halfway point (halftime).
-
C.
decidingGoalMinute
Indicates the minute in a match when a goal is scored that ultimately decides the outcome (e.g., the winning or decisive goal).
-
D.
gameWinningScoreTimeRemaining
chosen
Indicates the amount of time left in the game when the decisive, game-winning score was made.
-
E.
finalHomeGameResult
Indicates the outcome of an entity’s last home game in a given context or season.
- 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef0b6e0c8190ad6a335ee804829c |
completed | Feb. 28, 2026, 1:35 p.m. |
| PD | Predicate disambiguation | batch_69a2eddb98e081909efcf9f0a955a908 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.