Triple

T16803266
Position Surface form Disambiguated ID Type / Status
Subject Zanskar Valley E408411 entity
Predicate mainTown P13187 FINISHED
Object Padum E411288 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: Padum | Statement: [Zanskar Valley, mainTown, Padum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Padum
Context triple: [Zanskar Valley, mainTown, Padum]
  • A. Padum chosen
    Padum is a remote town in the Zanskar region of Ladakh, India, serving as the administrative and cultural center for the surrounding high-altitude Himalayan valley.
  • B. Rangpo
    Rangpo is a small town in the Indian state of Sikkim, known as a key gateway to the region and an important transit and trade point near the Sikkim–West Bengal border.
  • C. Phaplu
    Phaplu is a small town in Nepal’s Solukhumbu region that serves as a quieter gateway for trekkers heading toward the Everest region and Everest Base Camp.
  • D. Phuentsholing
    Phuentsholing is a major Bhutanese border town and commercial hub located on the frontier with India, serving as a key gateway into the country.
  • E. Punakha
    Punakha is a historic town in western Bhutan that served as the country’s former capital and is known for the majestic Punakha Dzong at the meeting of two rivers.
  • 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_69d88393905081908d00a86b99996ac8 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3b2ca46f88190b56e81d75012496c completed April 18, 2026, 4:35 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00c29ea9fc81909087cdf28c9c9fc0 completed May 10, 2026, 5:38 p.m.
Created at: April 10, 2026, 5:22 a.m.