Triple
T573183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Bowl XXV |
E13705
|
entity |
| Predicate | distanceOfMissedFieldGoal |
P16174
|
FINISHED |
| Object | 47 yards |
—
|
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: 47 yards | Statement: [Super Bowl XXV, distanceOfMissedFieldGoal, 47 yards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceOfMissedFieldGoal Context triple: [Super Bowl XXV, distanceOfMissedFieldGoal, 47 yards]
-
A.
gameWinningFieldGoalDistance
Indicates the distance from which a decisive, game-winning field goal was successfully kicked.
-
B.
decisiveTouchdownScorer
Indicates the player who scored the touchdown that ultimately determined the outcome of the game.
-
C.
touchdownsScored
Indicates the number of touchdowns that an entity has scored.
-
D.
numberOfGoals
Indicates the total count of goals scored or achieved by an entity in a given context.
-
E.
gameWinningKicker
Indicates that an entity serves as the kicker responsible for securing the decisive, game-winning score in a contest.
- 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b4ae0988190bdd0ad428b784d85 |
completed | March 1, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69a494c4969c819080375d08f9eec50c |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a498dd579081908e02368a4c5efc8c |
completed | March 1, 2026, 7:51 p.m. |
Created at: March 1, 2026, 7:33 p.m.