Triple
T7056869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Ijen |
E164113
|
entity |
| Predicate | sulfurFlamesCause |
P52514
|
FINISHED |
| Object | burning sulfuric gases |
—
|
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: burning sulfuric gases | Statement: [Mount Ijen, sulfurFlamesCause, burning sulfuric gases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sulfurFlamesCause Context triple: [Mount Ijen, sulfurFlamesCause, burning sulfuric gases]
-
A.
fireEffect
chosen
Indicates that one entity produces, causes, or is associated with a fire-related impact or consequence on another entity.
-
B.
fireType
Indicates that one entity has a specific classification or category related to fire (e.g., type, kind, or nature of fire).
-
C.
hasFumaroles
Indicates the presence of fumaroles (openings emitting volcanic gases or steam) associated with an entity.
-
D.
hasEternalFlame
Indicates that an entity possesses or maintains a flame that is intended to burn perpetually without being extinguished.
-
E.
eruptionEffect
Indicates the impact or consequences that an eruption has on its surrounding environment, systems, or entities.
- 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_69c68861678881909961ddf4d779f750 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e4a3c36c819080942c59f1830ae8 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bdc1f08190975fcdbbb1854d1e |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:38 p.m.