Triple
T25681440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arjuno-Welirang volcanic complex |
E643949
|
entity |
| Predicate | hasActiveFumaroles |
P2407
|
FINISHED |
| Object | Welirang 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: Welirang crater | Statement: [Arjuno-Welirang volcanic complex, hasActiveFumaroles, Welirang crater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasActiveFumaroles Context triple: [Arjuno-Welirang volcanic complex, hasActiveFumaroles, Welirang crater]
-
A.
hasFumaroles
chosen
Indicates the presence of fumaroles (openings emitting volcanic gases or steam) associated with an entity.
-
B.
hasVolcanicActivity
Indicates that the subject exhibits or is associated with ongoing or past volcanic processes, such as eruptions, lava flows, or related geothermal activity.
-
C.
hasLavaDomes
Indicates that the subject volcano possesses one or more lava domes as part of its structure or eruptive features.
-
D.
hasVolcanicVents
Indicates that one entity possesses or contains volcanic vents associated with another entity or location.
-
E.
hasVolcano
Indicates that one entity possesses, contains, or is the location of a volcano.
- 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_69e77e8046888190b07ffa58c7e2c37a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 21, 2026, 7:59 p.m.