Triple
T33288968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amazigh dance |
E852262
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Amazigh culture element |
C41874
|
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 culture element Context triple: [Amazigh dance, instanceOf, Amazigh culture element]
-
A.
Amazigh cultural heritage
chosen
Amazigh cultural heritage encompasses the traditional languages, arts, social customs, and ancestral knowledge of the Indigenous Amazigh (Berber) peoples of North Africa, reflecting their historical continuity, identity, and relationship with their environment.
-
B.
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.
-
C.
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.
-
D.
Amazigh people
The Amazigh people are the Indigenous inhabitants of North Africa, characterized by a shared Berber language continuum, distinct cultural traditions, and a long history predating Arab and European influences in the region.
-
E.
Tuareg cultural symbol
A Tuareg cultural symbol is any visual, material, or performative emblem—such as jewelry motifs, indigo garments, script, or desert-related icons—that expresses and communicates the identity, values, history, and social structure of Tuareg people.
- 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:32 a.m.