Triple
T9940357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kudryavy Volcano |
E194062
|
entity |
| Predicate | hasPersistentFumaroles |
P2407
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Kudryavy Volcano, hasPersistentFumaroles, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPersistentFumaroles Context triple: [Kudryavy Volcano, hasPersistentFumaroles, true]
-
A.
hasFumaroles
chosen
Indicates the presence of fumaroles (openings emitting volcanic gases or steam) associated with an entity.
-
B.
hasLavaDomes
Indicates that the subject volcano possesses one or more lava domes as part of its structure or eruptive features.
-
C.
hasVolcano
Indicates that one entity possesses, contains, or is the location of a volcano.
-
D.
hasVolcanicActivity
Indicates that the subject exhibits or is associated with ongoing or past volcanic processes, such as eruptions, lava flows, or related geothermal activity.
-
E.
hasHydrothermalActivity
Indicates that a location or geological feature exhibits hydrothermal activity, such as the circulation of heated water or fluids associated with geothermal processes.
- 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_69ca82e409348190a393777356b80a2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb60f4ffc8190bfe916bb4a7bf5c5 |
completed | April 2, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9428cc81909b4b4938566d78a7 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:44 p.m.