Triple
T4189661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1951 National League tie-breaker playoff |
E89001
|
entity |
| Predicate | decidingHomeRunInning |
P8285
|
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: [1951 National League tie-breaker playoff, decidingHomeRunInning, bottom of the ninth inning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decidingHomeRunInning Context triple: [1951 National League tie-breaker playoff, decidingHomeRunInning, bottom of the ninth inning]
-
A.
decisiveGameBatter
chosen
Indicates that a batter participated in a game situation that was decisive in determining the final outcome of the contest.
-
B.
homeRunType
Indicates the specific kind of home run that was hit in a baseball play (e.g., solo, two-run, three-run, grand slam).
-
C.
clinchingHomeRunType
Indicates the specific type or category of a home run that clinches or decisively secures a game, series, or title.
-
D.
RunsBattedIn
Indicates the number of runs a batter causes to score as a direct result of their plate appearance or action.
-
E.
homeRunDerbyChampion
Indicates that the subject is the winner of a home run derby 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_69aed9569a4481908b6c1fcec2a11e21 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af04b009dc8190abda3f149a5b16fa |
completed | March 9, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69af01935064819096b7619f42e164dd |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:46 p.m.