Triple
T26776080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nationalist attack on Blair House |
E670122
|
entity |
| Predicate | hasFatality |
P130516
|
FINISHED |
| Object | Leslie Coffelt |
—
|
NE NERFINISHED |
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: Leslie Coffelt | Statement: [Nationalist attack on Blair House, hasFatality, Leslie Coffelt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFatality Context triple: [Nationalist attack on Blair House, hasFatality, Leslie Coffelt]
-
A.
fatalInjury
Indicates that an entity causes or sustains an injury that directly results in death.
-
B.
fatallyDamaged
Indicates that an entity has been harmed or impaired to such an extent that death is inevitable or has already occurred as a result of the damage.
-
C.
causedFatalities
chosen
Indicates that the referenced event or action directly resulted in one or more deaths.
-
D.
deathResultedIn
Indicates that one event, action, or condition caused or led directly to a particular death as its outcome.
-
E.
deathOutcome
Indicates that an event, condition, or action results in the death of the affected entity.
- 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 27, 2026, 4:04 a.m.