Triple
T31279924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hackleburg, Alabama |
E797633
|
entity |
| Predicate | tornadoEventFatalities |
P130516
|
FINISHED |
| Object | multiple fatalities |
—
|
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: multiple fatalities | Statement: [Hackleburg, Alabama, tornadoEventFatalities, multiple fatalities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tornadoEventFatalities Context triple: [Hackleburg, Alabama, tornadoEventFatalities, multiple fatalities]
-
A.
tornadoFatalities1997
Indicates the number of fatalities caused by tornadoes in the year 1997.
-
B.
majorTornadoEvent
Indicates that a tornado event is of significant intensity or impact, typically meeting defined thresholds for severity or damage.
-
C.
notableDeathTollEvent
Indicates that an event is characterized by causing an unusually large or historically significant number of deaths.
-
D.
causedFatalities
chosen
Indicates that the referenced event or action directly resulted in one or more deaths.
-
E.
deathTollEstimate
Indicates an estimated number of deaths attributed to a particular event, cause, or period.
- 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_69f224def9088190a37034eab3daf57f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 9:13 p.m.