Triple
T33674049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elmer Smith |
E862707
|
entity |
| Predicate | battedGrandSlamIn |
P60115
|
FINISHED |
| Object | Game 5 of the 1920 World Series |
—
|
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: Game 5 of the 1920 World Series | Statement: [Elmer Smith, battedGrandSlamIn, Game 5 of the 1920 World Series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battedGrandSlamIn Context triple: [Elmer Smith, battedGrandSlamIn, Game 5 of the 1920 World Series]
-
A.
battedIn
chosen
Indicates that one participant caused a run to score in a baseball context, typically by successfully hitting the ball so that a runner crosses home plate.
-
B.
battedBy
Indicates that an entity is the one who performed the batting action on another entity (e.g., a ball being batted by a player).
-
C.
opponentBatterInFamousHomeRun
Indicates that the subject was the opposing batter involved in a specific, well-known home run event.
-
D.
battedLeadoff
Indicates that an entity served as the first batter in the lineup for a team in a particular game or context.
-
E.
battedInWorldSeries
Indicates that the subject participated as a batter in at least one game of a World Series.
- 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fa3efc1881909cc0775bce4c1e08 |
completed | May 3, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:43 a.m.