Triple
T20826811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1962 World Series |
E512723
|
entity |
| Predicate | finalOutInning |
P54553
|
FINISHED |
| Object | bottom of the ninth inning |
—
|
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: bottom of the ninth inning | Statement: [1962 World Series, finalOutInning, bottom of the ninth inning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalOutInning Context triple: [1962 World Series, finalOutInning, bottom of the ninth inning]
-
A.
subsequentInningOutcome
Indicates the result or event that occurs in the inning immediately following a given reference inning.
-
B.
finalManOfTheMatch
Indicates that the referenced person was chosen as the ultimate or concluding Man of the Match for a particular game or series.
-
C.
halfInning
chosen
Indicates the specific offensive or defensive segment of an inning in a game, typically distinguishing the top (visiting team at bat) from the bottom (home team at bat).
-
D.
perfectGameInnings
Indicates that the referenced innings constitute a perfect game, where no opposing batter successfully reaches base.
-
E.
finalHomeGameResult
Indicates the outcome of an entity’s last home game in a given context or season.
- 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_69e0b4ce39108190a6e8e5df4f1c8dc5 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2fe54608190a061274bf4316610 |
completed | April 21, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:41 p.m.