Triple
T539162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1993 World Series |
E12390
|
entity |
| Predicate | clinchingHomeRunType |
P16645
|
FINISHED |
| Object | walk-off 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: walk-off home run | Statement: [1993 World Series, clinchingHomeRunType, walk-off home run]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clinchingHomeRunType Context triple: [1993 World Series, clinchingHomeRunType, walk-off home run]
-
A.
homeRuns
Indicates the number of home runs a player hits, or that a specific home run event occurs, in a baseball context.
-
B.
winningHomeRunHitter
Indicates the player who hit the home run that ultimately decided the victory for their team in a game.
-
C.
careerHomeRuns
Indicates the total number of home runs an entity has hit over the entire span of their professional career.
-
D.
decisiveGameBatter
Indicates that a batter participated in a game situation that was decisive in determining the final outcome of the contest.
-
E.
losingPitcher
Indicates that the subject is the pitcher who was charged with the loss in a baseball game.
- F. None of above. chosen
Provenance (4 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b67c308190a1a225ab7c4b74c6 |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a49857e1148190aa782b82675cf0b5 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.