Triple
T18362317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scott Brosius hit two home runs in Game 3 |
E439948
|
entity |
| Predicate | goAheadHomeRunInning |
P130814
|
FINISHED |
| Object | 8th 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: 8th inning | Statement: [Scott Brosius hit two home runs in Game 3, goAheadHomeRunInning, 8th inning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goAheadHomeRunInning Context triple: [Scott Brosius hit two home runs in Game 3, goAheadHomeRunInning, 8th inning]
-
A.
game7DecisiveHomeRunInning
Indicates the inning in which a decisive home run was hit during game 7 of a series.
-
B.
battingSideForHomeRuns
Indicates the batting side (e.g., left-handed, right-handed, switch) from which a player hit their home runs.
-
C.
RunsBattedIn
Indicates the number of runs a batter causes to score as a direct result of their plate appearance or action.
-
D.
game7WinningRunBattedInBy
Indicates that the specified player drove in the run that provided the decisive margin of victory in Game 7 of a series.
-
E.
subsequentInningOutcome
Indicates the result or event that occurs in the inning immediately following a given reference inning.
- 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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e516dd973c8190857c588ab9ad9daf |
completed | April 19, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a1bda48190a9cd1db436d4be62 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:37 a.m.