Triple
T27478547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolf Volcano |
E693532
|
entity |
| Predicate | eruptionType_2015 |
P2063
|
FINISHED |
| Object | fissure eruption on southeastern flank |
—
|
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: fissure eruption on southeastern flank | Statement: [Wolf Volcano, eruptionType_2015, fissure eruption on southeastern flank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eruptionType_2015 Context triple: [Wolf Volcano, eruptionType_2015, fissure eruption on southeastern flank]
-
A.
volcanismType
chosen
Indicates the specific kind or style of volcanic activity or processes associated with an entity.
-
B.
eruption1902Type
Indicates the specific classification or type of the 1902 eruption event associated with an entity.
-
C.
eruptionVolcano
Indicates that a volcanic eruption event is occurring at or is associated with a specific volcano.
-
D.
eruptionVEI
Indicates the Volcanic Explosivity Index (VEI) assigned to a particular volcanic eruption event.
-
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_69ef5381f2648190a2392d0fab833095 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 12:58 p.m.