Triple
T10099285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1920 World Series |
E215955
|
entity |
| Predicate | unassistedTriplePlayInning |
P92420
|
FINISHED |
| Object | fifth 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: fifth inning | Statement: [1920 World Series, unassistedTriplePlayInning, fifth inning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unassistedTriplePlayInning Context triple: [1920 World Series, unassistedTriplePlayInning, fifth inning]
-
A.
inningOfThirdHomeRun
Indicates the specific inning during which a player's third home run in a game was hit.
-
B.
battedIn
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.
-
C.
RunsBattedIn
Indicates the number of runs a batter causes to score as a direct result of their plate appearance or action.
-
D.
notablePlayType
Indicates that a particular type or category of play is especially significant or characteristic for the subject.
-
E.
isBattingTripleCrown
Indicates that a player is simultaneously leading a league in batting average, home runs, and runs batted in.
- 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_69ca83a4947c8190823a7495dc5d96ed |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd07d686481908d9bb91392954474 |
completed | April 2, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9b853c8190a2af993ce9b21309 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd5150ae98819086c4f822114b4e2c |
completed | April 1, 2026, 5:09 p.m. |
Created at: March 30, 2026, 9:02 p.m.