Triple

T19660422
Position Surface form Disambiguated ID Type / Status
Subject Nyiragongo Territory E472063 entity
Predicate hasHazardMonitoring P82386 FINISHED
Object volcano monitoring by Goma Volcano Observatory 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: volcano monitoring by Goma Volcano Observatory | Statement: [Nyiragongo Territory, hasHazardMonitoring, volcano monitoring by Goma Volcano Observatory]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHazardMonitoring
Context triple: [Nyiragongo Territory, hasHazardMonitoring, volcano monitoring by Goma Volcano Observatory]
  • A. hasHazardManagement
    Indicates that an entity has measures, systems, or responsibilities in place to control, mitigate, or respond to identified hazards.
  • B. monitorsHazardType chosen
    Indicates that an entity observes, tracks, or keeps watch over a specified type or category of hazard.
  • C. hasHazardLevel
    Indicates that an entity is associated with a specified degree or category of risk or danger.
  • D. hasObjectiveHazards
    Indicates that an entity is associated with concrete, externally verifiable dangers or risks.
  • E. hasNotableHazard
    Indicates that an entity is associated with a significant risk, danger, or harmful condition that is noteworthy or exceptional.
  • 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_69d8e51395348190ac1416d46dfc6db0 completed April 10, 2026, 11:54 a.m.
NER Named-entity recognition batch_69e6414993ac8190b6da3702b1924b24 completed April 20, 2026, 3:07 p.m.
PD Predicate disambiguation batch_69e514e941008190898d978d7bde91e4 completed April 19, 2026, 5:46 p.m.
Created at: April 10, 2026, 1:45 p.m.