Triple

T4731266
Position Surface form Disambiguated ID Type / Status
Subject Mahanadi River E105012 entity
Predicate hasBarrage P11345 FINISHED
Object Jobra Barrage E413246 NE 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: Jobra Barrage | Statement: [Mahanadi River, hasBarrage, Jobra Barrage]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jobra Barrage
Context triple: [Mahanadi River, hasBarrage, Jobra Barrage]
  • A. Jobra Barrage chosen
    Jobra Barrage is a major irrigation and flood-control structure on the Mahanadi River near Cuttack in Odisha, India.
  • B. Kota Barrage
    Kota Barrage is a major irrigation and water-regulation dam located near Kota in Rajasthan, India, built across the Chambal River.
  • C. Tajewala Barrage
    Tajewala Barrage was an older irrigation and water diversion structure on the Yamuna River in Haryana, India, that was eventually superseded by the modern Hathni Kund Barrage.
  • D. Kosi Barrage
    Kosi Barrage is a major flood-control and irrigation structure built across the Kosi River near the India–Nepal border.
  • E. Guddu Barrage
    Guddu Barrage is a major irrigation and flood-control structure on the Indus River in Pakistan, crucial for distributing water to agricultural lands in Sindh and Balochistan.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69bd43ee52048190b81a4f066534ffb3 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd64629bc081908754aa8a2630091f completed March 20, 2026, 3:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69be10a9386c81908557fe4feb190e8a completed March 21, 2026, 3:29 a.m.
Created at: March 20, 2026, 1:19 p.m.