Triple
T20808854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2017 MLB All-Star Game |
E512240
|
entity |
| Predicate | MVPHomeRunType |
P46257
|
FINISHED |
| Object | solo home run |
—
|
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: solo home run | Statement: [2017 MLB All-Star Game, MVPHomeRunType, solo home run]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MVPHomeRunType Context triple: [2017 MLB All-Star Game, MVPHomeRunType, solo home run]
-
A.
homeRunType
chosen
Indicates the specific kind of home run that was hit in a baseball play (e.g., solo, two-run, three-run, grand slam).
-
B.
MVPHomeRunInning
Indicates the inning in which a Most Valuable Player (MVP) hit a home run in a game.
-
C.
MVPHomeRunLeagueFaced
Indicates that a league’s pitchers faced by a player during a season are associated with that player’s MVP-winning home run performance.
-
D.
MVPHomeRunTeamFaced
Indicates the team that an MVP award winner hit a home run against.
-
E.
MVPHomeRunRunsBattedIn
Indicates that the MVP player hit a home run on the play and was credited with one or more runs batted in (RBIs).
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2d199888190b8b190c928f510b7 |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:40 p.m.