Triple
T30832912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Unzen |
E785271
|
entity |
| Predicate | 1792DisasterDeaths |
P116006
|
FINISHED |
| Object | over 14,000 |
—
|
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 14,000 | Statement: [Mount Unzen, 1792DisasterDeaths, over 14,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 1792DisasterDeaths Context triple: [Mount Unzen, 1792DisasterDeaths, over 14,000]
-
A.
1792EruptionDeaths
chosen
Indicates that the referenced entities are connected through deaths caused by the volcanic eruption that occurred in the year 1792.
-
B.
notableDeathTollEvent
Indicates that an event is characterized by causing an unusually large or historically significant number of deaths.
-
C.
railDisasterCasualties
Indicates the number of people killed or injured as a result of a specific rail disaster.
-
D.
1792EruptionCaused
Indicates that one event or process was caused by the volcanic eruption that occurred in 1792.
-
E.
numberOfDeathsInNotableEvent
Indicates the total count of deaths that occurred as a result of a specified notable 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_69f224b73d8c81908129383bfb397c87 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6913c10f881909fee1f70a4fe9ad0 |
completed | May 3, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:44 p.m.