Triple
T26487122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saleaula |
E664851
|
entity |
| Predicate | affectedByEruptionOf |
P53970
|
FINISHED |
| Object | Mauga Afi |
—
|
NE NERFINISHED |
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: Mauga Afi | Statement: [Saleaula, affectedByEruptionOf, Mauga Afi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectedByEruptionOf Context triple: [Saleaula, affectedByEruptionOf, Mauga Afi]
-
A.
eruptionImpact
chosen
Indicates the effects or consequences that a volcanic eruption has on surrounding entities, environments, or systems.
-
B.
eruptionCoincidedWith
Indicates that a volcanic eruption occurred at the same time or within the same temporal interval as another specified event or condition.
-
C.
associatedVolcano
Indicates that there is a specific volcano linked or connected to the referenced entity, such as by location, impact, or relevance.
-
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_69ee883bc85481909885f92415cbce33 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 12:31 a.m.