Triple
T6666443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeffrey Maier interference play |
E151614
|
entity |
| Predicate | finalGameResult |
P10213
|
FINISHED |
| Object | Yankees win in extra innings |
—
|
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: Yankees win in extra innings | Statement: [Jeffrey Maier interference play, finalGameResult, Yankees win in extra innings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalGameResult Context triple: [Jeffrey Maier interference play, finalGameResult, Yankees win in extra innings]
-
A.
finalHomeGameResult
Indicates the outcome of an entity’s last home game in a given context or season.
-
B.
finalScore
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
C.
finalGameLeague
Indicates that a game is the concluding or championship match within a particular league or league season.
-
D.
gameOutcome
chosen
Indicates the result or final status of a game, such as which side won, lost, or if it ended in a draw.
-
E.
finalScoreWinner
Indicates that the referenced entity is the winner as determined by the final score of a game, match, 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_69c687f71fc081909dbd45d6377f6045 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce738fe88190a5557900efeec7ec |
completed | March 27, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69c6ad09974c81908784300ae218961f |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:02 p.m.