Triple

T15449741
Position Surface form Disambiguated ID Type / Status
Subject Sun Koshi E370117 entity
Predicate confluenceWith P2416 FINISHED
Object Bhote Koshi E226331 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: Bhote Koshi | Statement: [Sun Koshi, confluenceWith, Bhote Koshi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bhote Koshi
Context triple: [Sun Koshi, confluenceWith, Bhote Koshi]
  • A. Itahari
    Itahari is a rapidly growing commercial and transportation hub city in eastern Nepal, located at the junction of major highways connecting the region.
  • B. Dudh Koshi
    Dudh Koshi is a glacier-fed river in eastern Nepal that flows from the Everest region and is renowned for its milky white waters and challenging whitewater rapids.
  • C. Bhote Koshi River chosen
    The Bhote Koshi River is a steep, fast-flowing Himalayan river in northeastern Nepal renowned for its dramatic gorges, white-water rafting, and proximity to the Everest region.
  • D. Sudur
    Sudur is a settlement located within the Gusar District of Azerbaijan.
  • E. Ghandruk
    Ghandruk is a picturesque Gurung village in Nepal’s Annapurna region, known for its traditional culture, mountain views, and popularity as a trekking destination.
  • 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_69d85a19180081909925012fbf4e62a3 completed April 10, 2026, 2:02 a.m.
NER Named-entity recognition batch_69e03ef9334c81908541e231b43eb012 completed April 16, 2026, 1:44 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff3d42977881909ed07b58c029cbe9 completed May 9, 2026, 1:57 p.m.
Created at: April 10, 2026, 3:21 a.m.