Triple
T28580624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2009 NFC Championship |
E723363
|
entity |
| Predicate | gameDecidedBy |
P3221
|
FINISHED |
| Object | Garrett Hartley 40-yard field goal in overtime |
—
|
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: Garrett Hartley 40-yard field goal in overtime | Statement: [2009 NFC Championship, gameDecidedBy, Garrett Hartley 40-yard field goal in overtime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameDecidedBy Context triple: [2009 NFC Championship, gameDecidedBy, Garrett Hartley 40-yard field goal in overtime]
-
A.
decidingGameWinner
chosen
Indicates that an event, action, or process determines which participant is the winner of a game.
-
B.
gameWinner
Indicates which participant or team has won a particular game or match.
-
C.
gameOutcome
Indicates the result or final status of a game, such as which side won, lost, or if it ended in a draw.
-
D.
finalMatchDecidedBy
Indicates that the outcome of a final match is determined by a specific method, event, or deciding factor.
-
E.
decidingGameLoser
Indicates that the referenced entity is the loser in the decisive or final game that determines the overall outcome of a series or competition.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f650cbb3348190977e970d2986a846 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 4:14 a.m.