Triple
T10290202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Double X |
E241342
|
entity |
| Predicate | hasBattingHand |
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: [Double X, hasBattingHand, right-handed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBattingHand Context triple: [Double X, hasBattingHand, right-handed]
-
A.
battingHand
chosen
Indicates the handedness a player uses when batting, such as right-handed, left-handed, or switch.
-
B.
usesPitchingHandedness
Indicates that an entity performs pitching using a specified handedness (e.g., left-handed or right-handed).
-
C.
carriedInRightOrLeftHand
Indicates that an entity is being held and transported either in the right hand or in the left hand of an agent.
-
D.
battingPosition
Indicates the specific order or spot in which a player appears in a batting lineup or batting order.
-
E.
battingSideForHomeRuns
Indicates the batting side (e.g., left-handed, right-handed, switch) from which a player hit their home runs.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f117708190928f92ae2611d724 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:41 a.m.