Triple
T19333236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Tabasaran |
E483550
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tabasaran dialect |
C41943
|
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: Tabasaran dialect Context triple: [Northern Tabasaran, instanceOf, Tabasaran dialect]
-
A.
Pulaar dialect
The Pulaar dialect is a regional variety of the Fula language spoken primarily by the Fula people in parts of West Africa, characterized by distinct phonological, lexical, and grammatical features.
-
B.
Goral dialect
Goral dialect is a group of closely related Slavic vernaculars spoken by the Goral people in the mountainous regions along the Polish-Slovak border, characterized by features of Polish, Slovak, and other neighboring languages.
-
C.
Oshiwambo dialect
Oshiwambo dialect is a regional linguistic variety of the Oshiwambo language, characterized by distinct phonological, lexical, and grammatical features used by specific communities in northern Namibia and southern Angola.
-
D.
Ipai-Tipai dialect
The Ipai-Tipai dialect is a variant of the Yuman language continuum spoken by the Kumeyaay (Ipai and Tipai) people of southern California and northern Baja California, characterized by closely related but distinct regional speech forms.
-
E.
Bulu dialect
The Bulu dialect is a regional variety of the Bulu language spoken by the Bulu people, primarily in southern Cameroon, characterized by its distinct phonological, lexical, and grammatical features within the Beti-Bulu linguistic continuum.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:33 p.m.