Triple
T28754080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volcán Teneguía |
E731617
|
entity |
| Predicate | hasEruptionVEIRange |
P20135
|
FINISHED |
| Object | VEI 2 |
—
|
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 2 | Statement: [Volcán Teneguía, hasEruptionVEIRange, VEI 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEruptionVEIRange Context triple: [Volcán Teneguía, hasEruptionVEIRange, VEI 2]
-
A.
hasEruptionVolume
Indicates the relationship between a volcanic eruption event and the measured volume of material it releases.
-
B.
eruptionVEI
Indicates the Volcanic Explosivity Index (VEI) assigned to a particular volcanic eruption event.
-
C.
hasVolcanicExplosivityIndexRange
chosen
Indicates the range of Volcanic Explosivity Index (VEI) values within which a volcano’s or eruption’s explosiveness falls.
-
D.
eruptionPotential
Indicates the likelihood or capacity of something (typically a volcano or similar system) to erupt under given conditions.
-
E.
hasEruptionEpisodes
Indicates that an entity (such as a volcano or geyser) undergoes one or more distinct eruption events over time.
- 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 6:08 a.m.