Triple
T29696292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arkabi dialect |
E751360
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of the Laz language |
C56101
|
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 Laz language Context triple: [Arkabi dialect, instanceOf, regional variety of the Laz language]
-
A.
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.
-
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 Pamona language
A regional variety of the Pamona language is a geographically distinct form of Pamona characterized by systematic differences in pronunciation, vocabulary, and sometimes grammar, while remaining mutually intelligible with other Pamona varieties.
-
D.
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.
-
E.
Lezgic language
A Lezgic language is a member of a subgroup of the Northeast Caucasian language family, spoken primarily in southern Dagestan (Russia) and northern Azerbaijan, characterized by complex consonant systems and rich case morphology.
- 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_69f0d6266f8481909e70bb41cda18587 |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 7:20 p.m.