Triple
T26413141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teneguía |
E664013
|
entity |
| Predicate | eruptionCasualties |
P53970
|
FINISHED |
| Object | one indirect fatality in 1971 eruption |
—
|
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: one indirect fatality in 1971 eruption | Statement: [Teneguía, eruptionCasualties, one indirect fatality in 1971 eruption]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eruptionCasualties Context triple: [Teneguía, eruptionCasualties, one indirect fatality in 1971 eruption]
-
A.
eruptionImpact
chosen
Indicates the effects or consequences that a volcanic eruption has on surrounding entities, environments, or systems.
-
B.
eruptionVolcano
Indicates that a volcanic eruption event is occurring at or is associated with a specific volcano.
-
C.
eruptionPhenomena
Indicates the specific observable events or manifestations that occur during a volcanic eruption.
-
D.
eruptionObserved
Indicates that an eruption event has been witnessed, detected, or recorded by an observer or observing system.
-
E.
notableEruption
Indicates that a volcano or geothermal feature has experienced an eruption considered historically or scientifically significant.
- 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_69ee883a04ec81908883c4559f8c7e24 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 26, 2026, 11:39 p.m.