Triple
T32108586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kakching dialect |
E820054
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of Meitei language |
C61451
|
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: regional variety of Meitei language Context triple: [Kakching dialect, instanceOf, regional variety of Meitei language]
-
A.
regional variety of Kokborok
A regional variety of Kokborok is a localized form of the Kokborok language characterized by distinct phonological, lexical, and sometimes grammatical features specific to a particular geographic area or community.
-
B.
Meitei language
The Meitei language, also known as Manipuri, is a Tibeto-Burman language primarily spoken in the Indian state of Manipur and surrounding regions, serving as the state's official language and a key marker of Meitei cultural identity.
-
C.
Khasi language variety
A Khasi language variety is a specific form or dialect of the Khasi language, distinguished by unique phonological, lexical, or grammatical features associated with particular regions or communities.
-
D.
regional variety of Mandar language
A regional variety of Mandar language is a localized form of the Mandar language distinguished by unique phonological, lexical, and sometimes grammatical features associated with a specific geographic area or community.
-
E.
regional variety of Siwu language
A regional variety of the Siwu language is a geographically and socially distinct form of Siwu characterized by systematic differences in pronunciation, vocabulary, and sometimes grammar from other Siwu-speaking areas.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:27 a.m.