Triple
T19332985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kubachi |
E483542
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Dargin language variety |
C38621
|
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: Dargin language variety Context triple: [Kubachi, instanceOf, Dargin language variety]
-
A.
Dargwa language variety
chosen
A Dargwa language variety is a specific regional or social form of the Dargwa language, characterized by distinct phonological, lexical, and grammatical features within the broader Dargwa linguistic continuum.
-
B.
Yana language variety
Yana language variety refers to any of the related but distinct forms of the Yana language traditionally spoken by the Yana people of northern California, encompassing dialectal differences in phonology, vocabulary, and grammar.
-
C.
Gumuz language variety
A Gumuz language variety is a specific form or dialect of the Gumuz language, distinguished by its unique phonological, lexical, or grammatical features within the broader Gumuz linguistic continuum.
-
D.
regional variety of Burushaski
A regional variety of Burushaski is a geographically distinct form of the Burushaski language characterized by localized differences in pronunciation, vocabulary, and sometimes grammar while remaining mutually intelligible with other Burushaski varieties.
-
E.
Pamir language
The Pamir language is a group of Eastern Iranian languages spoken in the high-mountain Pamir region of Tajikistan, Afghanistan, and surrounding areas, characterized by significant diversity and archaic linguistic features.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:33 p.m.