Triple
T32402487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nevado del Ruiz |
E827988
|
entity |
| Predicate | deadliestEruptionIn |
P174034
|
FINISHED |
| Object | history of Colombia |
—
|
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: history of Colombia | Statement: [Nevado del Ruiz, deadliestEruptionIn, history of Colombia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deadliestEruptionIn Context triple: [Nevado del Ruiz, deadliestEruptionIn, history of Colombia]
-
A.
deadliestModernEruptionInJapan
Indicates that the subject is the volcanic eruption which caused the greatest number of deaths in Japan in modern times.
-
B.
lastEruption
Indicates the time or event corresponding to the most recent eruption associated with a given entity.
-
C.
oneOfDeadliestLaharDisasters
chosen
Indicates that the event is among the most deadly lahar (volcanic mudflow) disasters in terms of human casualties or impact.
-
D.
notableEruption
Indicates that a volcano or geothermal feature has experienced an eruption considered historically or scientifically significant.
-
E.
GreatEruptionPeakMagnitude
Indicates the peak intensity or maximum magnitude reached during a Great Eruption 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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 12:53 a.m.