Triple
T11277964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2008 Chaitén eruption |
E266984
|
entity |
| Predicate | eruptionPhase |
P98890
|
FINISHED |
| Object | initial explosive phase in May 2008 |
—
|
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: initial explosive phase in May 2008 | Statement: [2008 Chaitén eruption, eruptionPhase, initial explosive phase in May 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eruptionPhase Context triple: [2008 Chaitén eruption, eruptionPhase, initial explosive phase in May 2008]
-
A.
eruptionSeriesOf
Indicates a relationship where a specific volcanic eruption is a member event within a broader series or sequence of related eruptions.
-
B.
eruptionDuration
Indicates the length of time that an eruption event lasts from its onset to its end.
-
C.
eruptionFormed
Indicates that one entity was created or brought into existence as a direct result of a volcanic eruption involving the other entity.
-
D.
eruptionReactivation
Indicates a renewed or resumed volcanic eruption activity after a period of quiescence.
-
E.
eruptionVEI
Indicates the Volcanic Explosivity Index (VEI) assigned to a particular volcanic eruption event.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e967ebb4819080b09ed3cec44e77 |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a240588190aa097298f951c915 |
completed | April 9, 2026, 11:04 a.m. |
| PDg | Predicate description generation | batch_69d796cf74308190a5b29d0dd82954a2 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:31 p.m.