Triple
T22058868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Carl Allison |
E545096
|
entity |
| Predicate | sufferedInjuryEvent |
P58567
|
FINISHED |
| Object | helicopter crash at Talladega Superspeedway in 1993 |
—
|
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: helicopter crash at Talladega Superspeedway in 1993 | Statement: [David Carl Allison, sufferedInjuryEvent, helicopter crash at Talladega Superspeedway in 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sufferedInjuryEvent Context triple: [David Carl Allison, sufferedInjuryEvent, helicopter crash at Talladega Superspeedway in 1993]
-
A.
injuredIn
chosen
Indicates that an entity sustained an injury as a result of a specified event, situation, or action.
-
B.
causeOfInjury
Indicates that one entity is the source or reason that another entity sustained an injury.
-
C.
injuryOccurredAt
Indicates that an injury took place at a specific location or during a particular event or time.
-
D.
hasInjuredPerson
Indicates that an entity has a person who has been harmed or injured associated with it.
-
E.
injuryType
Indicates the specific kind or category of injury associated with an entity or event.
- 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_69e11e3377c48190890c17407b9527d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1285ac9608190ab4f89d4ee7350d0 |
completed | April 28, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:27 p.m.