Triple
T8937228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koma Kulshan |
E212806
|
entity |
| Predicate | isVolcanoType |
P80402
|
FINISHED |
| Object | stratovolcano |
—
|
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: stratovolcano | Statement: [Koma Kulshan, isVolcanoType, stratovolcano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isVolcanoType Context triple: [Koma Kulshan, isVolcanoType, stratovolcano]
-
A.
isTypeOfVolcano
chosen
Indicates that one entity is classified as a specific type or category of volcano in relation to another entity.
-
B.
isVolcanic
Indicates that something is characterized by or related to volcanic activity, such as originating from, produced by, or associated with a volcano.
-
C.
containsVolcanoType
Indicates that a geographic area or feature includes at least one volcano of the specified type.
-
D.
isVolcanicEdificeOn
Indicates that a volcanic edifice is physically located on or built upon a specified surface or geological feature.
-
E.
isExplosiveVolcano
Indicates that a volcano is currently or typically capable of explosive eruptions, characterized by violent release of gas, ash, and pyroclastic material.
- 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_69ca839694c88190b324ffeb43d23b08 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66b3628881909544507628980c25 |
completed | April 1, 2026, 12:28 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 6:58 p.m.