Triple
T7684781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 Major League Baseball All-Star Game |
E174087
|
entity |
| Predicate | MVPHandedness |
P8296
|
FINISHED |
| Object | right-handed |
—
|
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: right-handed | Statement: [2013 Major League Baseball All-Star Game, MVPHandedness, right-handed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MVPHandedness Context triple: [2013 Major League Baseball All-Star Game, MVPHandedness, right-handed]
-
A.
usesPitchingHandedness
Indicates that an entity performs pitching using a specified handedness (e.g., left-handed or right-handed).
-
B.
battingHand
chosen
Indicates the handedness a player uses when batting, such as right-handed, left-handed, or switch.
-
C.
MVPNationality
Indicates that an entity’s nationality is associated with a specific Most Valuable Player (MVP) recognition or context.
-
D.
MVPposition
Indicates the position or role in which an entity served when it was recognized as the Most Valuable Player (MVP).
-
E.
MVPBats
Indicates that an entity is recognized as the Most Valuable Player (MVP) specifically for their performance in batting.
- 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_69c6995840408190a19de6c51090f46f |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7048b0b448190889bd40e0a38e51a |
completed | March 27, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69c701618d3481908be84b76f36ac5a1 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 4:02 p.m.