Triple

T23343079
Position Surface form Disambiguated ID Type / Status
Subject Everest region E591784 entity
Predicate contains P35 FINISHED
Object Tengboche NE NERFINISHED

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: Tengboche | Statement: [Everest region, contains, Tengboche]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tengboche
Context triple: [Everest region, contains, Tengboche]
  • A. Tengboche chosen
    Tengboche is a Himalayan village in northeastern Nepal best known for its important Buddhist monastery and as a popular stop on the trekking route to Everest.
  • B. Pangboche
    Pangboche is a high-altitude Sherpa village in Nepal’s Khumbu region, known as a traditional stop on the trekking route to Everest Base Camp.
  • C. Dingboche
    Dingboche is a high-altitude Sherpa village in Nepal’s Everest region, commonly used as an acclimatization stop on the trekking route to Everest Base Camp.
  • D. Helambu
    Helambu is a culturally rich highland region of central Nepal known for its Sherpa villages, Buddhist monasteries, and scenic Himalayan landscapes.
  • E. Goecha La
    Goecha La is a high mountain pass in the eastern Himalayas of Sikkim, India, renowned as a trekking destination offering close views of Mount Kanchenjunga.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e25d20e3d08190bcede87673cafb25 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1983431f08190b0078728d44872a8 completed April 29, 2026, 5:33 a.m.
Created at: April 17, 2026, 5:18 p.m.