Triple
T10855396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tungurahua |
E256255
|
entity |
| Predicate | volcanicExplosivityIndexMax |
P15603
|
FINISHED |
| Object | VEI 4 (historical eruptions) |
—
|
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: VEI 4 (historical eruptions) | Statement: [Tungurahua, volcanicExplosivityIndexMax, VEI 4 (historical eruptions)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: volcanicExplosivityIndexMax Context triple: [Tungurahua, volcanicExplosivityIndexMax, VEI 4 (historical eruptions)]
-
A.
hasVolcanicExplosivityIndexRange
Indicates the range of Volcanic Explosivity Index (VEI) values within which a volcano’s or eruption’s explosiveness falls.
-
B.
eruptionVEI
chosen
Indicates the Volcanic Explosivity Index (VEI) assigned to a particular volcanic eruption event.
-
C.
eruptionHeight
Indicates the vertical distance or altitude reached by an eruption from its source.
-
D.
hasEruptionVolume
Indicates the relationship between a volcanic eruption event and the measured volume of material it releases.
-
E.
magmaticVolume
Indicates the amount of magma involved or produced in a magmatic process or 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75135df24819090ce43afa3ea9b38 |
completed | April 9, 2026, 7:11 a.m. |
| PD | Predicate disambiguation | batch_69d70d2b51448190bae748ed6c23edde |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:20 p.m.