Triple
T32176651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karymsky caldera system |
E821867
|
entity |
| Predicate | dominantVolcano |
P181174
|
FINISHED |
| Object | Karymsky volcano |
—
|
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: Karymsky volcano | Statement: [Karymsky caldera system, dominantVolcano, Karymsky volcano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantVolcano Context triple: [Karymsky caldera system, dominantVolcano, Karymsky volcano]
-
A.
isStratovolcanoOf
Indicates that a volcano is a stratovolcano specifically associated with, or located on, a particular geographic or administrative entity.
-
B.
oneOfMostActiveVolcanoesIn
Indicates that a volcano is among the most active volcanoes located within a specified geographic area or region.
-
C.
volcanoRank
Indicates the relative position or classification of a volcano within an ordered ranking system, such as by size, activity, or hazard level.
-
D.
volcanoName
Indicates that an entity is identified by the proper name of a volcano.
-
E.
isHighestVolcanoIn
Indicates that a volcano has the greatest elevation among all volcanoes within a specified geographic area or region.
- F. None of above. chosen
Provenance (4 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
| PDg | Predicate description generation | batch_69f762651e088190baa21f25378a6065 |
completed | May 3, 2026, 2:57 p.m. |
Created at: May 1, 2026, 12:34 a.m.