Triple
T16443835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fuego Volcano |
E399373
|
entity |
| Predicate | 2018EruptionImpact |
P28560
|
FINISHED |
| Object | caused significant casualties |
—
|
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: caused significant casualties | Statement: [Fuego Volcano, 2018EruptionImpact, caused significant casualties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2018EruptionImpact Context triple: [Fuego Volcano, 2018EruptionImpact, caused significant casualties]
-
A.
eruptionImpact
Indicates the effects or consequences that a volcanic eruption has on surrounding entities, environments, or systems.
-
B.
lastEruptionImpact
chosen
Indicates the effect or consequences resulting from the most recent volcanic eruption.
-
C.
eruptionPhenomena
Indicates the specific observable events or manifestations that occur during a volcanic eruption.
-
D.
GreatEruptionPeakMagnitude
Indicates the peak intensity or maximum magnitude reached during a Great Eruption event.
-
E.
eruptionPotential
Indicates the likelihood or capacity of something (typically a volcano or similar system) to erupt under given conditions.
- 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32cd9d474819091b4a80de1019c54 |
completed | April 18, 2026, 7:03 a.m. |
| PD | Predicate disambiguation | batch_69e227048d608190a4205eae3117629a |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.