Triple

T35089708
Position Surface form Disambiguated ID Type / Status
Subject Mount Siple E1012682 entity
Predicate hasVolcanicHazardLevel P182510 FINISHED
Object poorly constrained 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: poorly constrained | Statement: [Mount Siple, hasVolcanicHazardLevel, poorly constrained]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasVolcanicHazardLevel
Context triple: [Mount Siple, hasVolcanicHazardLevel, poorly constrained]
  • A. hasVolcanicHazardMap
    Indicates that a location or area is associated with an existing volcanic hazard map that documents potential volcanic risks there.
  • B. hasVolcanicActivity
    Indicates that the subject exhibits or is associated with ongoing or past volcanic processes, such as eruptions, lava flows, or related geothermal activity.
  • C. hasVolcanicAlertLevelSystem
    Indicates that an entity employs or is associated with a system for classifying and communicating levels of volcanic alert or hazard.
  • D. hasVolcano
    Indicates that one entity possesses, contains, or is the location of a volcano.
  • E. hasVolcanicLandform
    Indicates that one entity possesses, contains, or is characterized by a volcanic landform (such as a volcano, caldera, or lava plateau).
  • 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_69f76dd432ec8190969bc32acfc152b1 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78dbf72648190a4971a558e9d1889 completed May 3, 2026, 6:02 p.m.
PD Predicate disambiguation batch_69f78b8f4cc08190b49fccd798cb25d7 completed May 3, 2026, 5:53 p.m.
PDg Predicate description generation batch_69f78ce43094819093857fc99f269afe completed May 3, 2026, 5:59 p.m.
Created at: May 3, 2026, 4:01 p.m.