Triple
T3214657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Game 6 (1993 World Series) |
E67360
|
entity |
| Predicate | inningOfWalkOff |
P15119
|
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: [Game 6 (1993 World Series), inningOfWalkOff, bottom of the ninth inning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inningOfWalkOff Context triple: [Game 6 (1993 World Series), inningOfWalkOff, bottom of the ninth inning]
-
A.
walkOffInning
chosen
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.
-
B.
walkOffRBI
Indicates a game-ending run batted in (RBI) that immediately wins the game for the batting team in their final at-bat.
-
C.
walkOffPitcherFaced
Indicates that a pitcher was the one facing the batter who produced a walk-off outcome that ended the game.
-
D.
walkOffHomeRunGame
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.
-
E.
walkOff
Indicates that an entity departs or leaves a place or situation by walking away from it.
- 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_69ad858ac36c81909962589cd277d6e2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adab085a408190af9fb40acca31a5f |
completed | March 8, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69ad9e09b83881908801d79c3d9254f9 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.