Triple

T11369202
Position Surface form Disambiguated ID Type / Status
Subject Machapuchare E269296 entity
Predicate near P350 FINISHED
Object Pokhara E187800 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: Pokhara | Statement: [Machapuchare, near, Pokhara]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pokhara
Context triple: [Machapuchare, near, Pokhara]
  • A. Pokhara chosen
    Pokhara is a major lakeside city in central Nepal, known as a gateway to the Annapurna mountain range and a hub for trekking and adventure tourism.
  • B. Nepalgunj
    Nepalgunj is a major city in southwestern Nepal known as a commercial and transportation hub near the Indian border.
  • C. Patan
    Patan is an ancient city in the Kathmandu Valley of Nepal, renowned for its rich Newar culture, traditional arts, and historic Durbar Square filled with temples and palaces.
  • D. Kathmandu
    Kathmandu is the capital and largest city of Nepal, serving as the country’s political, cultural, and economic center.
  • E. Bhaktapur
    Bhaktapur is an ancient Newar city in the Kathmandu Valley of Nepal, renowned for its well-preserved medieval architecture, rich cultural heritage, and historic Durbar Square.
  • 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_69d6aacca1048190b39dbbc2174616fa completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7ea89e1148190b0ca29db9d7e2cbd completed April 9, 2026, 6:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69e5567b67f88190b0412e30b346d36d completed April 19, 2026, 10:26 p.m.
Created at: April 8, 2026, 9:33 p.m.