Triple
T4037506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buck Weaver |
E83860
|
entity |
| Predicate | batsAndThrowsStyle |
P41780
|
FINISHED |
| Object | switch-hitter and right-handed thrower |
—
|
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: switch-hitter and right-handed thrower | Statement: [Buck Weaver, batsAndThrowsStyle, switch-hitter and right-handed thrower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: batsAndThrowsStyle Context triple: [Buck Weaver, batsAndThrowsStyle, switch-hitter and right-handed thrower]
-
A.
bats
Indicates that one entity hits or strikes another entity, typically using a bat or similar implement.
-
B.
usesBatAndBall
Indicates that the action or activity involves the use of both a bat and a ball together.
-
C.
batsOrThrowsInCollege
Indicates that, in a college sports context, the person’s batting side and/or throwing arm is specified.
-
D.
throwingHand
Indicates which hand (left or right) an entity primarily uses to throw.
-
E.
batsFromSide
chosen
Indicates that one entity performs a batting action from a specified side or orientation (e.g., left-handed or right-handed).
- 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_69aed92f7cf0819098e0539bdcc3767f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb3656f08190aa5286d951013646 |
completed | March 9, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69aef900386481909d04555a9ec9b0e3 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:36 p.m.