Triple
T24648899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amazigh linguistic continuum |
E610192
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Amazigh language group |
C6447
|
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 group Context triple: [Amazigh linguistic continuum, instanceOf, Amazigh language group]
-
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.
Amazigh language variety
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.
-
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
chosen
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.
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_69e2c4d350a481909170482bc2ce6af9 |
completed | April 17, 2026, 11:40 p.m. |
Created at: April 18, 2026, 2:33 a.m.