Triple
T18300296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rich Hill |
E438340
|
entity |
| Predicate | notableInjuryHistory |
P3816
|
FINISHED |
| Object | elbow injuries |
—
|
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: elbow injuries | Statement: [Rich Hill, notableInjuryHistory, elbow injuries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableInjuryHistory Context triple: [Rich Hill, notableInjuryHistory, elbow injuries]
-
A.
hasInjuries
chosen
Indicates that an entity has sustained one or more physical or bodily injuries.
-
B.
injuredIn
Indicates that an entity sustained an injury as a result of a specified event, situation, or action.
-
C.
injuryInvolvedPlayer
Indicates that a specific player is involved in, affected by, or associated with a particular injury event.
-
D.
injuryYear
Indicates the year in which an injury occurred or was recorded for the entity.
-
E.
wasSidelinedBy
Indicates that one entity was removed from an active or central role by another entity, typically in favor of others or to reduce its influence or participation.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5017e88cc8190a969eb628ca1b496 |
completed | April 19, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.