Triple
T6668425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standard Moroccan Amazigh |
E151663
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Amazigh language variety |
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: Amazigh language variety Context triple: [Standard Moroccan Amazigh, instanceOf, Amazigh language variety]
-
A.
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.
-
B.
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.
-
C.
Berber language branch
The Berber language branch comprises a group of closely related Afroasiatic languages and dialects traditionally spoken by the indigenous Amazigh peoples across North Africa, from Morocco and Algeria to Libya, Tunisia, Mali, and Niger.
-
D.
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.
-
E.
Berber language grouping
A Berber language grouping is a conceptual class that encompasses the related Afroasiatic languages spoken by Berber (Amazigh) peoples across North Africa, classified together based on shared historical, structural, and lexical features.
- 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_69c687f71fc081909dbd45d6377f6045 |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 2:02 p.m.