Triple
T21036114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cerro Miñiques |
E518192
|
entity |
| Predicate | isVolcanicEdifice |
P26901
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Cerro Miñiques, isVolcanicEdifice, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isVolcanicEdifice Context triple: [Cerro Miñiques, isVolcanicEdifice, yes]
-
A.
isVolcanicEdificeOn
Indicates that a volcanic edifice is physically located on or built upon a specified surface or geological feature.
-
B.
isVolcanic
chosen
Indicates that something is characterized by or related to volcanic activity, such as originating from, produced by, or associated with a volcano.
-
C.
isTypeOfVolcano
Indicates that one entity is classified as a specific type or category of volcano in relation to another entity.
-
D.
isShieldVolcano
Indicates that the subject is classified as a shield volcano, a type of volcano characterized by broad, gently sloping sides formed by low-viscosity lava flows.
-
E.
isStratovolcanoOf
Indicates that a volcano is a stratovolcano specifically associated with, or located on, a particular geographic or administrative entity.
- 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_69e0b503275c8190afd9a163f997c709 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc865ca88190abf336ee9012fa77 |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:02 p.m.