Triple
T22570031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Promi Lepcha |
E558053
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Lepcha language |
C46518
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: variety of Lepcha language Context triple: [Promi Lepcha, instanceOf, variety of Lepcha language]
-
A.
variety of the Ladin language
A variety of the Ladin language is a regional or local form of Ladin distinguished by its own phonological, lexical, and sometimes grammatical features while remaining mutually intelligible with other Ladin varieties.
-
B.
variety of Lezgian language
A variety of the Lezgian language is a regional or social form of Lezgian distinguished by systematic differences in pronunciation, vocabulary, and sometimes grammar while remaining mutually intelligible with other forms.
-
C.
Bhili language variety
A Bhili language variety is a specific regional or social form of the Bhili language, characterized by distinct phonological, lexical, and grammatical features within the broader Bhili linguistic continuum.
-
D.
variety of the Zhuang language
A variety of the Zhuang language is a distinct regional or social form of Zhuang characterized by its own phonological, lexical, and grammatical features while remaining mutually intelligible to varying degrees with other Zhuang varieties.
-
E.
variety of Kunama language
A variety of Kunama language is a distinct regional or social form of the Kunama language characterized by unique phonological, lexical, or grammatical features within the broader Kunama-speaking community.
- F. None of above. chosen
Provenance (1 batch)
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_69e11e5ae4ac8190b1f503457603d969 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:52 p.m.