Triple
T1997334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1988 World Series |
E43388
|
entity |
| Predicate | game1WalkOffHomeRunInning |
P8288
|
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: [1988 World Series, game1WalkOffHomeRunInning, bottom of the ninth inning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: game1WalkOffHomeRunInning Context triple: [1988 World Series, game1WalkOffHomeRunInning, bottom of the ninth inning]
-
A.
walkOffHomeRunGame
chosen
Indicates that a game is decided by a walk-off home run, where the home team hits a game-ending home run in their final at-bat to win.
-
B.
walkOffInning
Indicates that an offensive play in baseball ends the inning immediately by scoring the decisive run, causing the batting team to win in walk-off fashion.
-
C.
walkOffHomeRunHitter
Indicates that the subject is the batter who hit a game-ending (walk-off) home run.
-
D.
firstMLBGameResult
Indicates the outcome of an entity’s first game played in Major League Baseball, such as whether it was a win, loss, or other recorded result.
-
E.
homeRunInteraction
Indicates an interaction where a batter successfully hits a home run, establishing the event and its participants.
- 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_69a88714cf2c819081644be450b8356e |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb91055d88190a980e7b42e5895d4 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb79c97d48190b3147430ed39faa9 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.