Triple
T28333758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomonori Maeda |
E717602
|
entity |
| Predicate | fieldingHand |
P171456
|
FINISHED |
| Object | 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: right-handed thrower | Statement: [Tomonori Maeda, fieldingHand, right-handed thrower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldingHand Context triple: [Tomonori Maeda, fieldingHand, right-handed thrower]
-
A.
battingHand
Indicates the handedness a player uses when batting, such as right-handed, left-handed, or switch.
-
B.
fieldingAbility
Indicates the level or quality of an entity’s skill and effectiveness in performing fielding actions in a game or sport.
-
C.
usesPitchingHandedness
Indicates that an entity performs pitching using a specified handedness (e.g., left-handed or right-handed).
-
D.
leftFielder
Indicates the relationship where an entity serves in the defensive baseball position of left fielder for a team or in a specific game context.
-
E.
quarterbackHandedness
Indicates the throwing-hand preference (left- or right-handed) of a quarterback in the context of playing the position.
- F. None of above. chosen
Provenance (4 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 28, 2026, 12:34 a.m.