Triple
T12523786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1967 NFL Championship Game |
E299383
|
entity |
| Predicate | decidingPlayDistance |
P41442
|
FINISHED |
| Object | 1 yard |
—
|
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: 1 yard | Statement: [1967 NFL Championship Game, decidingPlayDistance, 1 yard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decidingPlayDistance Context triple: [1967 NFL Championship Game, decidingPlayDistance, 1 yard]
-
A.
decidingPlay
Indicates that an action or event serves as the critical play that determines the outcome of a game or contest.
-
B.
decidingPlayStartYardLine
Indicates the action or process of determining from which yard line a play in a game (typically football) will begin.
-
C.
decidingScoreDistance
chosen
Indicates the point or score difference by which a contest, game, or decision is ultimately determined.
-
D.
decidingPlayBallCarrier
Indicates that an agent is determining or designating which player will act as the ball carrier in a play.
-
E.
decidingGameNumber
Indicates the specific game in a series whose outcome determines the overall winner of the series.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d9540d7b788190a0d57b098e90e491 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.