Triple
T1842243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2006 NFC Wild Card Game |
E41201
|
entity |
| Predicate | gameWinningScoreDistance |
P2633
|
FINISHED |
| Object | 38-yard field goal |
—
|
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: 38-yard field goal | Statement: [2006 NFC Wild Card Game, gameWinningScoreDistance, 38-yard field goal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameWinningScoreDistance Context triple: [2006 NFC Wild Card Game, gameWinningScoreDistance, 38-yard field goal]
-
A.
gameWinningScore
Indicates that a particular score results in winning the game.
-
B.
gameWinningScoreType
chosen
Indicates the type or category of score (e.g., goal, point, run) that results in winning a game.
-
C.
pointsForWin
Indicates the number of points awarded to an entity for achieving a win in a given context or competition.
-
D.
gameWinningScoreTimeRemaining
Indicates the amount of time left in the game when the decisive, game-winning score was made.
-
E.
hasWinningScore
Indicates that one entity possesses a score that is sufficient to win in a given competition, game, or scoring context.
- 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.