Triple

T10153384
Position Surface form Disambiguated ID Type / Status
Subject Khumbu Glacier E232705 entity
Predicate languageOfToponym P15 FINISHED
Object Sherpa language E591786 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: Sherpa language | Statement: [Khumbu Glacier, languageOfToponym, Sherpa language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sherpa language
Context triple: [Khumbu Glacier, languageOfToponym, Sherpa language]
  • A. Sherpa language chosen
    The Sherpa language is a Tibetic language spoken primarily by the Sherpa people of Nepal’s Himalayan region, especially in areas around Mount Everest.
  • B. Tamang language
    Tamang language is a Sino-Tibetan language spoken primarily by the Tamang people of Nepal and surrounding regions.
  • C. Khaling language
    The Khaling language is a Kiranti Sino-Tibetan language spoken by the Khaling ethnic group in eastern Nepal, noted for its complex verbal morphology and rich consonant system.
  • D. Gurung language
    Gurung language is a Sino-Tibetan language spoken primarily by the Gurung people of central Nepal, especially in the Gandaki region.
  • E. Yamphu language
    The Yamphu language is a Kiranti Sino-Tibetan language spoken by the Yamphu ethnic community in eastern Nepal.
  • 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_69ca84885e48819088a31b127cf44904 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cdec376cd48190990862c56c3a4dce completed April 2, 2026, 4:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69d2e64b5a40819093f29ec34cb0a763 completed April 5, 2026, 10:46 p.m.
Created at: March 30, 2026, 9:08 p.m.