Triple
T33439349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1993 Midwest floods |
E856316
|
entity |
| Predicate | humanDeaths |
P1785
|
FINISHED |
| Object | over 40 |
—
|
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: over 40 | Statement: [1993 Midwest floods, humanDeaths, over 40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: humanDeaths Context triple: [1993 Midwest floods, humanDeaths, over 40]
-
A.
deathToll
chosen
Indicates the number of deaths resulting from a particular event, situation, or cause.
-
B.
causedFatalities
Indicates that the referenced event or action directly resulted in one or more deaths.
-
C.
deathDetails
Indicates the specific circumstances, causes, and contextual information associated with an entity’s death.
-
D.
causeOfDeath
Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
-
E.
deathCharacteristic
Indicates a characteristic, attribute, or quality specifically associated with a death event or the manner in which death occurred.
- 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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:37 a.m.