Triple
T6001257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1992 AFC Wild Card Game vs Buffalo Bills |
E133600
|
entity |
| Predicate | overtimeFinalScore |
P35409
|
FINISHED |
| Object | 41–38 |
—
|
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: 41–38 | Statement: [1992 AFC Wild Card Game vs Buffalo Bills, overtimeFinalScore, 41–38]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overtimeFinalScore Context triple: [1992 AFC Wild Card Game vs Buffalo Bills, overtimeFinalScore, 41–38]
-
A.
opponentFinalScore
Indicates the final score achieved by an opposing participant or team in a contest or game.
-
B.
finalAfterExtraTime
chosen
Indicates that the final outcome or result is determined after an additional period of extra time beyond the regular duration.
-
C.
overtimePlayed
Indicates that an activity, event, or game continued beyond its regular or scheduled duration into an additional overtime period.
-
D.
finalScore
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
E.
finalSecondLegScore
Indicates the score achieved in the second leg of a two-leg competition or matchup once that leg is completed.
- 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04ee7c0e08190a6e78969448b070a |
completed | March 22, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69c049e3316c819087ea635fa7ee8472 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:05 p.m.