Triple

T8309786
Position Surface form Disambiguated ID Type / Status
Subject Khumbu E194560 entity
Predicate language 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, language, Sherpa language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sherpa language
Context triple: [Khumbu, language, 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. 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.
  • C. Gurung language
    Gurung language is a Sino-Tibetan language spoken primarily by the Gurung people of central Nepal, especially in the Gandaki region.
  • D. Yamphu language
    The Yamphu language is a Kiranti Sino-Tibetan language spoken by the Yamphu ethnic community in eastern Nepal.
  • E. Angami language
    Angami language is a Sino-Tibetan language spoken primarily by the Angami Naga people in Nagaland, India, known for its rich oral traditions and complex tonal system.
  • 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_69ca82e613e88190bf8139669bbd0d53 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb7f2d2c30819095075940479b75a7 completed March 31, 2026, 8 a.m.
NED1 Entity disambiguation (via context triple) batch_69cd95665390819089c8becad018cf51 completed April 1, 2026, 10 p.m.
Created at: March 30, 2026, 5:54 p.m.