Triple

T15067789
Position Surface form Disambiguated ID Type / Status
Subject Karnali Province E379797 entity
Predicate hasMajorTown P316 FINISHED
Object Surkhet E1020859 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: Surkhet | Statement: [Karnali Province, hasMajorTown, Surkhet]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Surkhet
Context triple: [Karnali Province, hasMajorTown, Surkhet]
  • A. Surkhet chosen
    Surkhet is a major city in western Nepal that serves as the administrative and commercial hub of Karnali Province.
  • B. Nepalgunj
    Nepalgunj is a major city in southwestern Nepal known as a commercial and transportation hub near the Indian border.
  • C. 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.
  • D. Sankhuwasabha District
    Sankhuwasabha District is a mountainous district in eastern Nepal known for encompassing part of the Himalayas, including the area around Mount Makalu.
  • E. Ghorahi
    Ghorahi is a major city in western Nepal known as an administrative, commercial, and educational hub of the Dang Valley 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_69d85cd7683881908d405c1b5d7b4f7f completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69dedeebc7e48190a86b4f0afe8844bb completed April 15, 2026, 12:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69feae11d6648190bc9b5d4f520d694b completed May 9, 2026, 3:46 a.m.
Created at: April 10, 2026, 3:02 a.m.