Triple
T24304454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayt Ndhir dialect |
E612494
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Central Atlas Tamazight dialect |
C21166
|
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: Central Atlas Tamazight dialect Context triple: [Ayt Ndhir dialect, instanceOf, Central Atlas Tamazight dialect]
-
A.
Northern Berber language
A Northern Berber language is a member of the Berber branch of the Afroasiatic language family spoken primarily across the northern regions of North Africa, characterized by shared phonological, morphological, and syntactic features distinct from other Berber varieties.
-
B.
Berber language
Berber language is a branch of the Afroasiatic language family comprising several closely related languages spoken by the indigenous Amazigh peoples of North Africa.
-
C.
Amazigh language
The Amazigh language is a group of closely related Afroasiatic languages indigenous to North Africa, spoken by the Amazigh (Berber) people and characterized by rich oral traditions and the Tifinagh script.
-
D.
Amazigh language variety
chosen
An Amazigh language variety is a specific regional or social form of the Amazigh (Berber) language, characterized by distinct phonological, lexical, and grammatical features shared by its speech community.
-
E.
Saharan language
A Saharan language is a member of a small family of related languages spoken primarily in the central Sahara region of Africa, characterized by shared grammatical structures and vocabulary distinct from neighboring language families.
- 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_69e2d7d91bb48190bc5377d17a85fb21 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 1:29 a.m.