Triple
T35301781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lokon-Empung volcano |
E1019524
|
entity |
| Predicate | activeCrater |
P129350
|
FINISHED |
| Object | Tompaluan crater |
—
|
NE NERFINISHED |
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: Tompaluan crater | Statement: [Lokon-Empung volcano, activeCrater, Tompaluan crater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeCrater Context triple: [Lokon-Empung volcano, activeCrater, Tompaluan crater]
-
A.
mainCrater
Indicates that one crater is the primary or most significant crater associated with another crater or crater-related feature.
-
B.
hasActiveCrater
chosen
Indicates that the subject entity possesses at least one crater that is currently geologically or volcanically active.
-
C.
peakVolcanicActivity
Indicates the time or condition under which a volcano reaches its highest level of eruptive or geothermal activity.
-
D.
eruptionFocus
Indicates that an eruption event is centered on, originates from, or is primarily associated with a particular focal location or feature.
-
E.
neighboringCrater
Indicates that one crater is located adjacent to or very close to another crater, such that they are considered neighbors on a surface.
- 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_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:03 p.m.