Triple

T6564358
Position Surface form Disambiguated ID Type / Status
Subject Gonda E153864 entity
Predicate locatedNear P294 FINISHED
Object Ghaghara River E28899 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: Ghaghara River | Statement: [Gonda, locatedNear, Ghaghara River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ghaghara River
Context triple: [Gonda, locatedNear, Ghaghara River]
  • A. Ghaghara chosen
    Ghaghara is a major Himalayan river in northern India and Nepal that significantly contributes to the flow of the Ganges.
  • B. Subarnarekha River
    The Subarnarekha River is a significant river in eastern India that flows through the states of Jharkhand, West Bengal, and Odisha before emptying into the Bay of Bengal.
  • C. Parbati River
    The Parbati River is a Himalayan river in northern India that flows through the Parvati Valley of Himachal Pradesh before joining the Beas River.
  • D. Parbati River
    The Parbati River is a significant river in central India that contributes to the Chambal River system and supports agriculture and local ecosystems along its course.
  • E. Bindal River
    Bindal River is a small seasonal river flowing through Dehradun in Uttarakhand, India, known for its role in local drainage and frequent urban flooding concerns.
  • 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_69c6880cb35881909b763eb0125236b9 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6ae3b9ec8819080f3052556d95810 completed March 27, 2026, 4:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7006679688190af29dee17dcbf65d completed March 27, 2026, 10:10 p.m.
Created at: March 27, 2026, 1:52 p.m.