Triple

T10786563
Position Surface form Disambiguated ID Type / Status
Subject East Champaran district E254464 entity
Predicate containsTown P847 FINISHED
Object Sugauli E715141 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: Sugauli | Statement: [East Champaran district, containsTown, Sugauli]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sugauli
Context triple: [East Champaran district, containsTown, Sugauli]
  • A. Sugauli chosen
    Sugauli is a town in the Indian state of Bihar historically known as the place where the 1816 Treaty of Sugauli between the British East India Company and Nepal was concluded.
  • B. Maharajgunj
    Maharajgunj is a prominent neighborhood in Kathmandu, Nepal, known for hosting key national institutions and residential areas.
  • C. Ghorahi
    Ghorahi is a major city in western Nepal known as an administrative, commercial, and educational hub of the Dang Valley region.
  • D. Tikapur
    Tikapur is a town in far‑western Nepal known for its planned urban layout and the large riverside Tikapur Park along the Karnali River.
  • E. Itahari
    Itahari is a rapidly growing commercial and transportation hub city in eastern Nepal, located at the junction of major highways connecting the region.
  • 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_69d6aa609f008190a294200aefcb7bd5 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d732d5422481908d7ab833c6cbc879 completed April 9, 2026, 5:02 a.m.
NED1 Entity disambiguation (via context triple) batch_69de56199d088190938a72105540cf66 completed April 14, 2026, 2:58 p.m.
Created at: April 8, 2026, 9:17 p.m.