Triple
T6331476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Bowl XXIII |
E142390
|
entity |
| Predicate | gameDecidingPlay |
P54545
|
FINISHED |
| Object | Joe Montana touchdown pass to John Taylor |
—
|
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: Joe Montana touchdown pass to John Taylor | Statement: [Super Bowl XXIII, gameDecidingPlay, Joe Montana touchdown pass to John Taylor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameDecidingPlay Context triple: [Super Bowl XXIII, gameDecidingPlay, Joe Montana touchdown pass to John Taylor]
-
A.
decidingPlay
chosen
Indicates that an action or event serves as the critical play that determines the outcome of a game or contest.
-
B.
decidingGameWinner
Indicates that an event, action, or process determines which participant is the winner of a game.
-
C.
decidingGameNumber
Indicates the specific game in a series whose outcome determines the overall winner of the series.
-
D.
decidingGameCity
Indicates the city where the decisive or final game of a series, match, or competition takes place.
-
E.
decidingMatchFor
Indicates a relationship where one entity is chosen or determined as the appropriate or final match for another entity among possible alternatives.
- 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_69c008d4d8e88190ad301c05b08722ac |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06514cbe8819096dbeb17ccb3e3d5 |
completed | March 22, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:30 p.m.