Triple
T6083825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanggar Peninsula |
E135586
|
entity |
| Predicate | impactOf1815Eruption |
P53970
|
FINISHED |
| Object | regional devastation |
—
|
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: regional devastation | Statement: [Sanggar Peninsula, impactOf1815Eruption, regional devastation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactOf1815Eruption Context triple: [Sanggar Peninsula, impactOf1815Eruption, regional devastation]
-
A.
eruptionImpact
chosen
Indicates the effects or consequences that a volcanic eruption has on surrounding entities, environments, or systems.
-
B.
lastEruptionImpact
Indicates the effect or consequences resulting from the most recent volcanic eruption.
-
C.
oneOfLargestEruptionsOfCentury
Indicates that the event is among the most powerful volcanic eruptions that occurred within a given century.
-
D.
notableEruption
Indicates that a volcano or geothermal feature has experienced an eruption considered historically or scientifically significant.
-
E.
eruptionVEI
Indicates the Volcanic Explosivity Index (VEI) assigned to a particular volcanic eruption event.
- 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_69c0087bcc788190b20f093d3a6c60ec |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c057877b448190aa12d2484102eeaa |
completed | March 22, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c049f3b1ec8190bea67a7bec6442a5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:11 p.m.