Triple
T9644688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Карымский |
E233164
|
entity |
| Predicate | типВулкана |
P2063
|
FINISHED |
| Object | слоистый вулкан |
—
|
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: слоистый вулкан | Statement: [Карымский, типВулкана, слоистый вулкан]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: типВулкана Context triple: [Карымский, типВулкана, слоистый вулкан]
-
A.
volcanismType
chosen
Indicates the specific kind or style of volcanic activity or processes associated with an entity.
-
B.
typeOfVolcanicFeature
Indicates that one entity is classified as a specific kind or category of volcanic feature represented by the other entity.
-
C.
isStratovolcanoOf
Indicates that a volcano is a stratovolcano specifically associated with, or located on, a particular geographic or administrative entity.
-
D.
isStratovolcano
Indicates that the subject is a stratovolcano, i.e., a steep, conical volcano built from alternating layers of lava, ash, and other volcanic materials.
-
E.
isVolcanic
Indicates that something is characterized by or related to volcanic activity, such as originating from, produced by, or associated with 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_69ca848a5a908190aad251f4137b0c3a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b7fd2308190803a196ecdc80d76 |
completed | April 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b0263081908cf6df3eb07d71b0 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:12 p.m.