Triple
T5776551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1966 NFL Championship Game |
E127455
|
entity |
| Predicate | DallasFinalDriveResult |
P66384
|
FINISHED |
| Object | interception |
—
|
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: interception | Statement: [1966 NFL Championship Game, DallasFinalDriveResult, interception]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DallasFinalDriveResult Context triple: [1966 NFL Championship Game, DallasFinalDriveResult, interception]
-
A.
finalHomeGameResult
Indicates the outcome of an entity’s last home game in a given context or season.
-
B.
nextFinals
Indicates that one event, match, or stage directly follows another as the subsequent or upcoming finals in a sequence.
-
C.
finalsLosingTeam
Indicates the team that was defeated in the final match of a competition or tournament.
-
D.
finalNHLGame
Indicates that an NHL game is the last or concluding game in a specified series, season, or career context.
-
E.
completedLineToDallas
Indicates that a transportation or communication line has been fully constructed or established leading to Dallas.
- 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_69c008361fa88190aefa4dc41b051e7f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021d0c6088190ba670ddcdbf5ca3e |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c02ac9603481909e3fa295d7904a15 |
completed | March 22, 2026, 5:45 p.m. |
Created at: March 22, 2026, 3:50 p.m.