Triple

T27274370
Position Surface form Disambiguated ID Type / Status
Subject Konda River E688143 entity
Predicate hasFloodsIn P13044 FINISHED
Object spring 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: spring | Statement: [Konda River, hasFloodsIn, spring]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFloodsIn
Context triple: [Konda River, hasFloodsIn, spring]
  • A. hasFloodRisk
    Indicates that an entity is exposed to a potential or expected risk of flooding under certain conditions.
  • B. hasFloodRiskAreas
    Indicates that certain areas are subject to potential flooding or are classified as being at risk of flood events.
  • C. hasSeasonalFlooding chosen
    Indicates that an area regularly experiences flooding during specific, recurring times of the year.
  • D. hasFloodRiskRelevance
    Indicates that something is pertinent to, affects, or is used in assessing the risk or likelihood of flooding.
  • E. hasFloodplains
    Indicates that an area or region includes land that is subject to flooding, typically adjacent to a river or water body.
  • 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_69ef3558cf8881909595ef89daf6e14a completed April 27, 2026, 10:07 a.m.
NER Named-entity recognition batch_69f661b58ac48190907b6c6e9ccc2c59 completed May 2, 2026, 8:42 p.m.
PD Predicate disambiguation batch_69f660eea4648190b0d5e24293607813 completed May 2, 2026, 8:39 p.m.
Created at: April 27, 2026, 11:01 a.m.