Triple
T17246055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yordan Álvarez |
E418626
|
entity |
| Predicate | hasBattingType |
P96341
|
FINISHED |
| Object | left-handed power hitter |
—
|
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: left-handed power hitter | Statement: [Yordan Álvarez, hasBattingType, left-handed power hitter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBattingType Context triple: [Yordan Álvarez, hasBattingType, left-handed power hitter]
-
A.
battingType
chosen
Indicates the style or handedness with which a player bats (e.g., right-handed, left-handed, or both).
-
B.
battingAverageType
Indicates the type or category of a batting average associated with a player or performance (e.g., season, career, situational).
-
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.
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).
-
E.
hasPitchType
Indicates that an entity is associated with, or characterized by, a specific type or category of pitch.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e23b8948190870d0e6b4e55b4e3 |
completed | April 19, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.