Triple

T21854803
Position Surface form Disambiguated ID Type / Status
Subject Mahalangur Himal E539594 entity
Predicate region P40 FINISHED
Object Khumbu 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: Khumbu | Statement: [Mahalangur Himal, region, Khumbu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Khumbu
Context triple: [Mahalangur Himal, region, Khumbu]
  • A. Khumbu chosen
    Khumbu is a high-altitude region in northeastern Nepal famed for encompassing the Everest area and serving as the homeland of the Sherpa people.
  • B. Langtang Himal
    Langtang Himal is a prominent subrange of the Himalayas in north-central Nepal, known for its high peaks, glaciers, and popular trekking routes near the Tibetan border.
  • C. Langtang
    Langtang is a town in Plateau State, central Nigeria, known as the homeland of the Tarok people and for its strong tradition of producing military officers.
  • D. Kinnauri
    Kinnauri is a Tibeto-Burman language spoken primarily by the indigenous people of India’s Himalayan Kinnaur region.
  • E. Champawat
    Champawat is a town and district headquarters in the Kumaon region of Uttarakhand, India, known for its historical temples and scenic Himalayan setting.
  • 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_69e0c47829648190bbe2d1d7033768ec completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f0bd5ba9288190af962117124f6483 completed April 28, 2026, 1:59 p.m.
Created at: April 16, 2026, 6:56 p.m.