Triple
T8261453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurricane Irma |
E193203
|
entity |
| Predicate | fatalities_total |
P1785
|
FINISHED |
| Object | over 130 |
—
|
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 130 | Statement: [Hurricane Irma, fatalities_total, over 130]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fatalities_total Context triple: [Hurricane Irma, fatalities_total, over 130]
-
A.
casualtiesTotal
Indicates the total number of people killed and injured as a result of a particular event or incident.
-
B.
fatalitiesCategory
Indicates the classification of deaths associated with an event, incident, or condition into a specific category or severity level.
-
C.
deathToll
chosen
Indicates the number of deaths resulting from a particular event, situation, or cause.
-
D.
deathTollEstimate
Indicates an estimated number of deaths attributed to a particular event, cause, or period.
-
E.
fatalitiesOnboard
Indicates that the relationship specifies the number of people who died among those present on a particular vehicle or craft.
- 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_69ca82e081d48190986beaa51f498ab9 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7936b72c8190b998da033df611d1 |
completed | March 31, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69cb36b8707881909aca349230495a5a |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:49 p.m.