Triple

T32176664
Position Surface form Disambiguated ID Type / Status
Subject Karymsky caldera system E821867 entity
Predicate 1996EruptionFeature P173284 FINISHED
Object phreatomagmatic activity in Karymsky Lake 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: phreatomagmatic activity in Karymsky Lake | Statement: [Karymsky caldera system, 1996EruptionFeature, phreatomagmatic activity in Karymsky Lake]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: 1996EruptionFeature
Context triple: [Karymsky caldera system, 1996EruptionFeature, phreatomagmatic activity in Karymsky Lake]
  • A. 1991EruptionFeature
    Indicates a feature or characteristic specifically associated with the 1991 volcanic eruption.
  • B. eruptionFormed
    Indicates that one entity was created or brought into existence as a direct result of a volcanic eruption involving the other entity.
  • C. eruptionEvidence
    Indicates that there is observable or documented evidence supporting the occurrence of a volcanic eruption.
  • D. eruptionObserved
    Indicates that an eruption event has been witnessed, detected, or recorded by an observer or observing system.
  • E. eruption1902Type
    Indicates the specific classification or type of the 1902 eruption event associated with an entity.
  • 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_69f6ba7a3efc819084fb3c8175044458 completed May 3, 2026, 3:01 a.m.
PD Predicate disambiguation batch_69f6b3aa892481908d29283a074e6722 completed May 3, 2026, 2:32 a.m.
PDg Predicate description generation batch_69f6b42902a081909126c7322858a2b3 completed May 3, 2026, 2:34 a.m.
Created at: May 1, 2026, 12:34 a.m.