Triple
T20715429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Len Hutton |
E509156
|
entity |
| Predicate | battingAfterInjury |
P141221
|
FINISHED |
| Object | continued to bat with shortened left arm |
—
|
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: continued to bat with shortened left arm | Statement: [Len Hutton, battingAfterInjury, continued to bat with shortened left arm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battingAfterInjury Context triple: [Len Hutton, battingAfterInjury, continued to bat with shortened left arm]
-
A.
battedAgainstTeamAtTimeOfInjury
Indicates that a player batted against a specific team at the time when the player sustained an injury.
-
B.
battedForTeamAtTimeOfInjury
Indicates that a player was batting for a specific team at the time the injury occurred.
-
C.
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.
-
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.
battingType
Indicates the style or handedness with which a player bats (e.g., right-handed, left-handed, or both).
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1d12a9481909cce3711c1c2d9f8 |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:15 p.m.