Triple

T1488665
Position Surface form Disambiguated ID Type / Status
Subject Cumbre Vieja E29525 entity
Predicate hasVolcanicEdifice P6356 FINISHED
Object multiple overlapping cones 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: multiple overlapping cones | Statement: [Cumbre Vieja, hasVolcanicEdifice, multiple overlapping cones]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasVolcanicEdifice
Context triple: [Cumbre Vieja, hasVolcanicEdifice, multiple overlapping cones]
  • A. hasVolcano chosen
    Indicates that one entity possesses, contains, or is the location of a volcano.
  • 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. hasVolcanicActivity
    Indicates that the subject exhibits or is associated with ongoing or past volcanic processes, such as eruptions, lava flows, or related geothermal activity.
  • D. containsVolcanicRegion
    Indicates that one entity geographically includes or encompasses an area characterized by volcanic features or activity.
  • E. typeOfVolcanicFeature
    Indicates that one entity is classified as a specific kind or category of volcanic feature represented by the other 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_69a498da82e08190ba833330d05f380f completed March 1, 2026, 7:51 p.m.
NER Named-entity recognition batch_69a4c6a6095481909e9d406ac9a41828 completed March 1, 2026, 11:07 p.m.
PD Predicate disambiguation batch_69a4c48902808190a8028d359bcf123e completed March 1, 2026, 10:58 p.m.
Created at: March 1, 2026, 8:12 p.m.