Triple

T9921346
Position Surface form Disambiguated ID Type / Status
Subject Province No. 1 E187802 entity
Predicate containsCity P294 FINISHED
Object Dharan E673840 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: Dharan | Statement: [Province No. 1, containsCity, Dharan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dharan
Context triple: [Province No. 1, containsCity, Dharan]
  • A. Dharan chosen
    Dharan is a major city in eastern Nepal known for its role as a former British Gurkha recruitment center and as a gateway to the eastern hills.
  • B. Chanhudaro
    Chanhudaro is an archaeological site in present-day Pakistan known as a smaller but significant urban center of the Indus Valley Civilization, notable for its craft production and bead-making.
  • C. Katihar
    Katihar is a city in eastern India known as a major railway junction and commercial center in the state of Bihar.
  • D. Nepalgunj
    Nepalgunj is a major city in southwestern Nepal known as a commercial and transportation hub near the Indian border.
  • E. Nalapani
    Nalapani is a historic hilltop area near Dehradun in present-day Uttarakhand, India, known for its fortified position and association with early 19th-century Anglo-Nepalese conflict.
  • 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_69ca82b22a688190b52c75bd48429c10 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cdb56abbb88190a21b8b77f1a25b81 completed April 2, 2026, 12:16 a.m.
NED1 Entity disambiguation (via context triple) batch_69d20e019f788190a0106b60c8a39efa completed April 5, 2026, 7:23 a.m.
Created at: March 30, 2026, 8:42 p.m.