Triple
T2053130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1929 World Series |
E45613
|
entity |
| Predicate | notableInning |
P28663
|
FINISHED |
| Object | 10-run seventh inning in Game 4 |
—
|
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: 10-run seventh inning in Game 4 | Statement: [1929 World Series, notableInning, 10-run seventh inning in Game 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableInning Context triple: [1929 World Series, notableInning, 10-run seventh inning in Game 4]
-
A.
notableEventInning
chosen
Indicates the specific inning during which a notable or significant event occurred in a game.
-
B.
notablePitch
Indicates that an entity is recognized for having a particularly significant or noteworthy pitch, offer, or proposal in a given context.
-
C.
notableBatter
Indicates that the subject is a batter who is particularly prominent, distinguished, or noteworthy in the context of batting.
-
D.
notablePlay
Indicates that a particular play is especially famous, significant, or noteworthy in relation to the entity it is associated with.
-
E.
notablePlayType
Indicates that a particular type or category of play is especially significant or characteristic for the subject.
- 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_69a8891a19508190a12ef1e192308dcb |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb99196ec819096f491ac7732156a |
completed | March 7, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_69abb7abba508190b872f345d3ba51bb |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.