Triple
T32402303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armero tragedy |
E827984
|
entity |
| Predicate | timeOfMainLahar |
P191595
|
FINISHED |
| Object | around 23:30 local time |
—
|
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: around 23:30 local time | Statement: [Armero tragedy, timeOfMainLahar, around 23:30 local time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfMainLahar Context triple: [Armero tragedy, timeOfMainLahar, around 23:30 local time]
-
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.
oneOfDeadliestLaharDisasters
Indicates that the event is among the most deadly lahar (volcanic mudflow) disasters in terms of human casualties or impact.
-
D.
timeOfMainAssault
Indicates the specific time at which the primary or main assault event occurred.
-
E.
timeOfMainDeformation
Indicates the specific time or period during which the primary deformation event occurs.
- 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_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
| PDg | Predicate description generation | batch_69fce28a74508190aab36551094e8226 |
completed | May 7, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:52 a.m.