Triple
T32402296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armero tragedy |
E827984
|
entity |
| Predicate | deadliestVolcanicDisasterIn |
P87239
|
FINISHED |
| Object | Colombia |
—
|
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: Colombia | Statement: [Armero tragedy, deadliestVolcanicDisasterIn, Colombia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deadliestVolcanicDisasterIn Context triple: [Armero tragedy, deadliestVolcanicDisasterIn, Colombia]
-
A.
deadliestModernEruptionInJapan
Indicates that the subject is the volcanic eruption which caused the greatest number of deaths in Japan in modern times.
-
B.
oneOfLargestEruptionsOfCentury
Indicates that the event is among the most powerful volcanic eruptions that occurred within a given century.
-
C.
discoveredAsVolcano
Indicates that an entity was identified, recognized, or confirmed to be a volcano.
-
D.
worstNaturalDisasterIn
chosen
Indicates that a particular natural disaster is the most severe or damaging one that has occurred within a specified location or region.
-
E.
majorEruptionYear
Indicates the calendar year in which a volcano or similar geological feature experienced a major eruption.
- 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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c21bb0d081909644ca365aacfdfa |
completed | May 3, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:52 a.m.