Triple
T20401108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Randall David Johnson |
E500331
|
entity |
| Predicate | battedAndThrewCombination |
P96341
|
FINISHED |
| Object | bats right, throws left |
—
|
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: bats right, throws left | Statement: [Randall David Johnson, battedAndThrewCombination, bats right, throws left]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battedAndThrewCombination Context triple: [Randall David Johnson, battedAndThrewCombination, bats right, throws left]
-
A.
battedBy
Indicates that an entity is the one who performed the batting action on another entity (e.g., a ball being batted by a player).
-
B.
battingType
chosen
Indicates the style or handedness with which a player bats (e.g., right-handed, left-handed, or both).
-
C.
battedBallType
Indicates the specific kind of contact or trajectory resulting when a ball is hit (e.g., ground ball, fly ball, line drive).
-
D.
battedIn
Indicates that one participant caused a run to score in a baseball context, typically by successfully hitting the ball so that a runner crosses home plate.
-
E.
battedDoubles
Indicates that the subject hit a double in baseball, successfully reaching second base on a batted ball.
- 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_69e0b4a81bec8190b69adfdc1336a015 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6798e7a588190b60bd54260e540f4 |
completed | April 20, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:29 a.m.