Triple
T32402297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armero tragedy |
E827984
|
entity |
| Predicate | oneOfDeadliestLaharDisasters |
P174034
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Armero tragedy, oneOfDeadliestLaharDisasters, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oneOfDeadliestLaharDisasters Context triple: [Armero tragedy, oneOfDeadliestLaharDisasters, true]
-
A.
hasLahars
Indicates that an entity experiences, produces, or is associated with volcanic mudflows (lahars).
-
B.
hasPotentialForLahars
Indicates that one entity (typically a geographic or volcanic feature) is capable of producing or being affected by lahars under certain conditions.
-
C.
triggeredLandslides
Indicates that one entity caused or initiated landslides affecting another entity or area.
-
D.
worstNaturalDisasterIn
Indicates that a particular natural disaster is the most severe or damaging one that has occurred within a specified location or region.
-
E.
hasLaharWarningSystem
Indicates that an entity is equipped with a system designed to detect and warn about potential or ongoing lahars (volcanic mudflows).
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f6bb344bb48190a8089f29c0063ded |
completed | May 3, 2026, 3:04 a.m. |
Created at: May 1, 2026, 12:52 a.m.