Triple

T31196545
Position Surface form Disambiguated ID Type / Status
Subject Berber world E795339 entity
Predicate instanceOf P0 FINISHED
Object Amazigh cultural sphere 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 cultural sphere
Context triple: [Berber world, instanceOf, Amazigh cultural sphere]
  • 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 homeland
    The Amazigh homeland is the vast, historically continuous region of North Africa where Amazigh (Berber) peoples have lived for millennia, stretching from the Siwa Oasis in Egypt across the Sahara and Maghreb to the Canary Islands.
  • 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. 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.
  • 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_69f224d7a6a481908187c4362a8a525f completed April 29, 2026, 3:33 p.m.
Created at: April 29, 2026, 9:09 p.m.