Triple

T10149056
Position Surface form Disambiguated ID Type / Status
Subject Damodar River E232582 entity
Predicate historicallyProneTo P92510 FINISHED
Object flooding 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: flooding | Statement: [Damodar River, historicallyProneTo, flooding]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicallyProneTo
Context triple: [Damodar River, historicallyProneTo, flooding]
  • A. historicallyIn
    Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
  • B. historicallyConsidered
    Indicates that one entity has been regarded or classified in a particular way relative to another entity during a past historical period.
  • C. historicallyGivenTo
    Indicates that something was transferred or bestowed upon an entity at some point in the past, typically as recorded or recognized in historical accounts.
  • D. historicallyGivenIn
    Indicates that something was customarily or traditionally granted, presented, or assigned to something or someone in the past.
  • E. historicallyObservedIn
    Indicates that something has been recorded or documented as occurring, existing, or taking place within a particular historical context, period, or location.
  • 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_69ca84885e48819088a31b127cf44904 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cdec024da481908b8170fcf3b18e67 completed April 2, 2026, 4:09 a.m.
PD Predicate disambiguation batch_69cd4ba4f5d88190ba68e63be10b08c7 completed April 1, 2026, 4:45 p.m.
PDg Predicate description generation batch_69cd51bc440c819086320900701f87c2 completed April 1, 2026, 5:11 p.m.
Created at: March 30, 2026, 9:08 p.m.