Triple
T17725638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pat Burrell |
E442453
|
entity |
| Predicate | battedDoubles |
P128754
|
FINISHED |
| Object | 303 |
—
|
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: 303 | Statement: [Pat Burrell, battedDoubles, 303]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battedDoubles Context triple: [Pat Burrell, battedDoubles, 303]
-
A.
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.
-
B.
battedWalks
Indicates that one entity walked to first base as a result of a plate appearance in which they were batting (i.e., received a base on balls while at bat).
-
C.
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).
-
D.
battedRuns
Indicates that a player scored a specified number of runs while batting in a cricket (or similar bat-and-ball) context.
-
E.
battedBallType
Indicates the specific kind of contact or trajectory resulting when a ball is hit (e.g., ground ball, fly ball, line drive).
- 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47489c59c8190bbffefad20dc6346 |
completed | April 19, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
| PDg | Predicate description generation | batch_69e3d37ab6988190bd326ea6f8dd4aaa |
completed | April 18, 2026, 6:54 p.m. |
Created at: April 10, 2026, 10:07 a.m.