Triple
T8251615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nyiragongo |
E192970
|
entity |
| Predicate | hasNotableEruptionImpact |
P53970
|
FINISHED |
| Object | 2002 lava flows destroyed parts of Goma |
—
|
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: 2002 lava flows destroyed parts of Goma | Statement: [Nyiragongo, hasNotableEruptionImpact, 2002 lava flows destroyed parts of Goma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableEruptionImpact Context triple: [Nyiragongo, hasNotableEruptionImpact, 2002 lava flows destroyed parts of Goma]
-
A.
eruptionImpact
chosen
Indicates the effects or consequences that a volcanic eruption has on surrounding entities, environments, or systems.
-
B.
notableEruption
Indicates that a volcano or geothermal feature has experienced an eruption considered historically or scientifically significant.
-
C.
lastEruptionImpact
Indicates the effect or consequences resulting from the most recent volcanic eruption.
-
D.
previousNotableEruption
Indicates that one volcanic eruption directly precedes another notable eruption in time.
-
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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78ca4b0881909bb1fb550dba59e7 |
completed | March 31, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69cb36b6d5548190b665a6cce14c69f7 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.