Triple
T18503960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaun Livingston |
E452151
|
entity |
| Predicate | sufferedMajorInjury |
P3816
|
FINISHED |
| Object | severe left knee injury on February 26, 2007 |
—
|
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: severe left knee injury on February 26, 2007 | Statement: [Shaun Livingston, sufferedMajorInjury, severe left knee injury on February 26, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sufferedMajorInjury Context triple: [Shaun Livingston, sufferedMajorInjury, severe left knee injury on February 26, 2007]
-
A.
injuredIn
Indicates that an entity sustained an injury as a result of a specified event, situation, or action.
-
B.
hasInjuredPerson
Indicates that an entity has a person who has been harmed or injured associated with it.
-
C.
hasInjuries
chosen
Indicates that an entity has sustained one or more physical or bodily injuries.
-
D.
fatalInjury
Indicates that an entity causes or sustains an injury that directly results in death.
-
E.
causeOfInjury
Indicates that one entity is the source or reason that another entity sustained an injury.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53341063c81908361b0eb78794145 |
completed | April 19, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.