Triple

T18201826
Position Surface form Disambiguated ID Type / Status
Subject Volcano Island E435807 entity
Predicate riskZoneDesignation P38433 FINISHED
Object Permanent Danger Zone 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: Permanent Danger Zone | Statement: [Volcano Island, riskZoneDesignation, Permanent Danger Zone]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: riskZoneDesignation
Context triple: [Volcano Island, riskZoneDesignation, Permanent Danger Zone]
  • A. riskZone
    Indicates that an entity is located within or associated with an area characterized by elevated danger, threat, or potential harm.
  • B. geologicalHazardZoneFor chosen
    Indicates a relationship where a specified area or zone is identified as being at risk from a particular geological hazard (such as earthquakes, landslides, or volcanic activity).
  • C. riskDomain
    Indicates that something belongs to, is associated with, or falls under a particular area or category of risk.
  • D. riskGroup
    Indicates that an entity belongs to a category of individuals or items that share an elevated level of risk relative to others.
  • E. hasRegionDesignation
    Indicates that an entity is assigned or associated with a specific regional classification or designation.
  • 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_69d8b90dba6481908e119eb9aa4ca0cb completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4e0d71f288190918ca78543118bbe completed April 19, 2026, 2:04 p.m.
PD Predicate disambiguation batch_69e4332155d88190b106d0dceb4554af completed April 19, 2026, 1:42 a.m.
Created at: April 10, 2026, 10:32 a.m.