Triple
T13093870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Lokon |
E310529
|
entity |
| Predicate | eruptionColumn |
P105661
|
FINISHED |
| Object | eruption plumes sometimes reaching several kilometers high |
—
|
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: eruption plumes sometimes reaching several kilometers high | Statement: [Mount Lokon, eruptionColumn, eruption plumes sometimes reaching several kilometers high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eruptionColumn Context triple: [Mount Lokon, eruptionColumn, eruption plumes sometimes reaching several kilometers high]
-
A.
eruptionHeight
Indicates the vertical distance or altitude reached by an eruption from its source.
-
B.
eruptionName
Indicates the specific name assigned to a volcanic eruption event associated with an entity.
-
C.
eruptionPhenomena
chosen
Indicates the specific observable events or manifestations that occur during a volcanic eruption.
-
D.
eruptionSeriesOf
Indicates a relationship where a specific volcanic eruption is a member event within a broader series or sequence of related eruptions.
-
E.
eruptionObserved
Indicates that an eruption event has been witnessed, detected, or recorded by an observer or observing system.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9813cd1b881909871a318fdd60672 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:03 p.m.