Triple
T15263125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Game 2 of the 2005 World Series |
E364834
|
entity |
| Predicate | walkOffHomeRunType |
P15118
|
FINISHED |
| Object | solo home run |
—
|
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: solo home run | Statement: [Game 2 of the 2005 World Series, walkOffHomeRunType, solo home run]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: walkOffHomeRunType Context triple: [Game 2 of the 2005 World Series, walkOffHomeRunType, solo home run]
-
A.
walkOffHomeRunHitter
Indicates that the subject is the batter who hit a game-ending (walk-off) home run.
-
B.
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.
-
C.
walkOffRBI
Indicates a game-ending run batted in (RBI) that immediately wins the game for the batting team in their final at-bat.
-
D.
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.
-
E.
walkOffType
chosen
Indicates the specific way in which a walk-off (a game-ending play or event) occurs or is classified.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0084fed0481908e452c89cba2be82 |
completed | April 15, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:14 a.m.