Triple
T1842143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miracle at the Meadowlands |
E41199
|
entity |
| Predicate | decidingPlayType |
P29019
|
FINISHED |
| Object | fumble return touchdown |
—
|
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: fumble return touchdown | Statement: [Miracle at the Meadowlands, decidingPlayType, fumble return touchdown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decidingPlayType Context triple: [Miracle at the Meadowlands, decidingPlayType, fumble return touchdown]
-
A.
decidingGameNumber
Indicates the specific game in a series whose outcome determines the overall winner of the series.
-
B.
decidingMatchFor
Indicates a relationship where one entity is chosen or determined as the appropriate or final match for another entity among possible alternatives.
-
C.
decisionType
Indicates the specific category or nature of a decision associated with an entity or event.
-
D.
playType
chosen
Indicates the specific category or style of play or performance associated with an event or action.
-
E.
decidingGameCity
Indicates the city where the decisive or final game of a series, match, or competition takes place.
- 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdb0d2c8190a67f584e67979fa3 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.