Triple

T23506322
Position Surface form Disambiguated ID Type / Status
Subject Bodish languages E572290 entity
Predicate hasMember P10 FINISHED
Object Lepcha language 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: Lepcha language | Statement: [Bodish languages, hasMember, Lepcha language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lepcha language
Context triple: [Bodish languages, hasMember, Lepcha language]
  • A. Lepcha language chosen
    The Lepcha language is an indigenous Sino-Tibetan language spoken primarily by the Lepcha people in parts of Sikkim and neighboring regions of India, Bhutan, and Nepal, known for its unique script and rich oral tradition.
  • B. Chamba language
    The Chamba language is a Niger-Congo language spoken by the Chamba people of Nigeria and Cameroon.
  • C. Rengma language
    Rengma language is a Tibeto-Burman language spoken primarily by the Rengma Naga people in the northeastern region of India.
  • D. Kumaoni language
    Kumaoni language is an Indo-Aryan language of the Central Pahari group spoken primarily in the Kumaon region of Uttarakhand, India.
  • E. Wancho language
    Wancho language is a Tibeto-Burman language spoken by the Wancho people of Arunachal Pradesh in northeastern India.
  • 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_69e245b5e4208190bac8a6509867e394 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1a9009ca081908c4cffb8c32293ec completed April 29, 2026, 6:45 a.m.
Created at: April 17, 2026, 6:07 p.m.