Triple
T35302179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Lokon and Mount Empung |
E1019533
|
entity |
| Predicate | typicalEruptionProduct |
P15890
|
FINISHED |
| Object | andesitic lava |
—
|
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: andesitic lava | Statement: [Mount Lokon and Mount Empung, typicalEruptionProduct, andesitic lava]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEruptionProduct Context triple: [Mount Lokon and Mount Empung, typicalEruptionProduct, andesitic lava]
-
A.
producedEruption
Indicates that an entity caused or generated a particular eruption event.
-
B.
materialErupted
Indicates that some material has been expelled or discharged forcefully from a source, such as through an eruption or sudden outburst.
-
C.
typicalLavaType
chosen
Indicates the usual or characteristic type of lava associated with a given volcanic feature, eruption, or context.
-
D.
eruptionVolcano
Indicates that a volcanic eruption event is occurring at or is associated with a specific volcano.
-
E.
eruptionPhenomena
Indicates the specific observable events or manifestations that occur during a volcanic eruption.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.