Triple
T38386076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Kam |
E899583
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of the Kam language |
C63163
|
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 the Kam language Context triple: [Northern Kam, instanceOf, variety of the Kam language]
-
A.
Kam language variety
chosen
A Kam language variety is a specific form or dialect of the Kam language, distinguished by its unique phonological, lexical, and grammatical features within the broader Kam linguistic continuum.
-
B.
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.
-
C.
Kunama language variety
A Kunama language variety is a specific regional or social form of the Kunama language, distinguished by its own characteristic phonological, lexical, and grammatical features within the broader Kunama linguistic continuum.
-
D.
variety of the Karbi language
A variety of the Karbi language is a distinct regional or social form of Karbi characterized by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other forms.
-
E.
variety of the Kayan language
A variety of the Kayan language is a distinct regional or social form of Kayan characterized by its own phonological, lexical, and grammatical features while remaining mutually intelligible to varying degrees with other Kayan varieties.
- F. None of above.
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_69f76e5c9b808190b486523f5c2f817d |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:31 p.m.