Triple
T11425363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaitén |
E270732
|
entity |
| Predicate | eruptivePhase |
P98890
|
FINISHED |
| Object | Plinian eruption 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: Plinian eruption in May 2008 | Statement: [Chaitén, eruptivePhase, Plinian eruption in May 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eruptivePhase Context triple: [Chaitén, eruptivePhase, Plinian eruption in May 2008]
-
A.
eruptionPhase
chosen
Indicates the specific stage or phase of development, activity, or progression within an eruption event.
-
B.
eruptionSeriesOf
Indicates a relationship where a specific volcanic eruption is a member event within a broader series or sequence of related eruptions.
-
C.
erupted
Indicates that a volcano or similar geological feature suddenly expelled lava, ash, gas, or other material in a violent outburst.
-
D.
eruptionFormed
Indicates that one entity was created or brought into existence as a direct result of a volcanic eruption involving the other entity.
-
E.
eruptiveEnvironment
Indicates the geological or environmental setting in which an eruption or eruptive activity occurs.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d806be9c2c819084da13101cbb6c81 |
completed | April 9, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69d7e71436f88190ac7e45a04ea5c987 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.