Triple

T36723944
Position Surface form Disambiguated ID Type / Status
Subject Cunene Province E907143 entity
Predicate hasClimateIssue P14203 FINISHED
Object drought risk 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: drought risk | Statement: [Cunene Province, hasClimateIssue, drought risk]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasClimateIssue
Context triple: [Cunene Province, hasClimateIssue, drought risk]
  • A. hasClimate
    Indicates that an entity possesses or is characterized by a particular type of climate or climatic conditions.
  • B. hasClimateContext
    Indicates that something is associated with, influenced by, or relevant to climate-related conditions, factors, or considerations.
  • C. hasClimateInfluence
    Indicates that one entity affects or contributes to the climate characteristics or climate-related conditions of another entity.
  • D. climaticChallenge chosen
    Indicates a relationship where an entity faces, contributes to, or is affected by significant difficulties or stresses arising from climate or weather conditions.
  • E. hasClimateSystem
    Indicates that one entity possesses or is characterized by a particular climate system.
  • 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_69f76e746e4c8190a0d05cc6d57a643e completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fdd5fba5048190b7d430ae2054a1fd completed May 8, 2026, 12:24 p.m.
PD Predicate disambiguation batch_69fdd35f76f88190a1854ea27132f9c7 completed May 8, 2026, 12:13 p.m.
Created at: May 3, 2026, 4:12 p.m.