Triple
T10496472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulusan Volcano |
E247549
|
entity |
| Predicate | eruptionMechanism |
P94472
|
FINISHED |
| Object | hydrothermal explosions |
—
|
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: hydrothermal explosions | Statement: [Bulusan Volcano, eruptionMechanism, hydrothermal explosions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eruptionMechanism Context triple: [Bulusan Volcano, eruptionMechanism, hydrothermal explosions]
-
A.
eruptiveEnvironment
Indicates the geological or environmental setting in which an eruption or eruptive activity occurs.
-
B.
volcanismType
Indicates the specific kind or style of volcanic activity or processes associated with an entity.
-
C.
eruptionVEI
Indicates the Volcanic Explosivity Index (VEI) assigned to a particular volcanic eruption event.
-
D.
eruptionFormed
Indicates that one entity was created or brought into existence as a direct result of a volcanic eruption involving the other entity.
-
E.
eruptionSeriesOf
Indicates a relationship where a specific volcanic eruption is a member event within a broader series or sequence of related eruptions.
- F. None of above. chosen
Provenance (4 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5098cd82c8190b44127a66c9c75ae |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8e24ac8190912c9f11b8bd3084 |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe46a6448190b061bc3545835cad |
completed | April 7, 2026, 12:53 p.m. |
Created at: April 6, 2026, 12:24 p.m.