Triple
T30572340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karanogai dialect |
E778151
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of the Nogai language |
C51706
|
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 the Nogai language Context triple: [Karanogai dialect, instanceOf, regional variety of the Nogai language]
-
A.
variety of the Nogai language
chosen
A variety of the Nogai language is a regional or social form of Nogai distinguished by specific phonological, lexical, or grammatical features while remaining mutually intelligible with other Nogai forms.
-
B.
regional variety of the Kumyk language
A regional variety of the Kumyk language is a geographically defined form of Kumyk that exhibits distinct phonological, lexical, or grammatical features while remaining mutually intelligible with other Kumyk dialects.
-
C.
regional variety of Lezgian
A regional variety of Lezgian is a geographically distinct form of the Lezgian language characterized by unique phonological, lexical, and grammatical features shared by speakers in a particular area.
-
D.
regional variety of the Laz language
A regional variety of the Laz language is a distinct form of Laz spoken in a specific geographic area, characterized by unique phonological, lexical, or grammatical features that differentiate it from other Laz dialects.
-
E.
regional variety of Jingpo language
A regional variety of the Jingpo language is a geographically or socially distinct form of Jingpo characterized by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Jingpo 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:22 p.m.