Triple
T13070268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1954 World Series over-the-shoulder catch often called "The Catch" |
E329436
|
entity |
| Predicate | batterBats |
P108295
|
FINISHED |
| Object | left-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: left-handed | Statement: [1954 World Series over-the-shoulder catch often called "The Catch", batterBats, left-handed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: batterBats Context triple: [1954 World Series over-the-shoulder catch often called "The Catch", batterBats, left-handed]
-
A.
usesWoodBats
Indicates that the subject performs an action or participates in an activity using bats made of wood rather than other materials.
-
B.
winnerBats
Indicates that the entity identified as the winner performs the action of batting.
-
C.
usesBatAndBall
Indicates that the action or activity involves the use of both a bat and a ball together.
-
D.
batter
Indicates that one entity physically strikes or beats another entity, typically with repeated or forceful blows.
-
E.
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.
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d980ee6130819095d835e7ff6a8c5b |
completed | April 10, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d980e622e8819087a69bfb1660dd64 |
completed | April 10, 2026, 10:59 p.m. |
Created at: April 9, 2026, 9 p.m.