Triple
T18362315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scott Brosius hit two home runs in Game 3 |
E439948
|
entity |
| Predicate | contributedRunsViaHR |
P14862
|
FINISHED |
| Object | 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: 4 | Statement: [Scott Brosius hit two home runs in Game 3, contributedRunsViaHR, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contributedRunsViaHR Context triple: [Scott Brosius hit two home runs in Game 3, contributedRunsViaHR, 4]
-
A.
careerRuns
Indicates the total number of runs a player has scored over the entire duration of their professional career.
-
B.
homeRuns
chosen
Indicates the number of home runs a player hits, or that a specific home run event occurs, in a baseball context.
-
C.
careerRunsScored
Indicates the total number of runs an entity has scored over the entire duration of their playing career.
-
D.
clinchingHomeRunRunsBattedIn
Indicates that a particular home run both clinches a game or series and accounts for specific runs batted in (RBIs) scored by the batter.
-
E.
hasLifelinesOrAssists
Indicates that one entity provides lifelines, help, or supportive interventions to another entity.
- 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_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. |
Created at: April 10, 2026, 10:37 a.m.