Triple

T8600719
Position Surface form Disambiguated ID Type / Status
Subject Tamasheq E203666 entity
Predicate closelyRelatedTo P37 FINISHED
Object Tamazight E164210 NE FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Tamazight | Statement: [Tamasheq, closelyRelatedTo, Tamazight]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tamazight
Context triple: [Tamasheq, closelyRelatedTo, Tamazight]
  • A. Tamazight chosen
    Tamazight is a branch of the Berber (Amazigh) languages of North Africa, encompassing several closely related varieties spoken across countries such as Morocco and Algeria.
  • B. Insular Tamazight
    Insular Tamazight is the extinct Berber language once spoken by the indigenous Guanche people of the Canary Islands.
  • C. Tashelhit
    Tashelhit is a variety of the Amazigh (Berber) language family spoken primarily in southwestern Morocco.
  • D. Beni Snous Tamazight
    Beni Snous Tamazight is a Zenati Berber variety traditionally spoken by the Beni Snous community in northwestern Algeria near the Moroccan border.
  • E. Tamazgha
    Tamazgha is the name used by many Amazigh (Berber) people for the broader North African homeland where their communities and cultures are rooted.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 batches)

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_69ca832b56948190ba751cec255308f1 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cc46d8ff408190acc7cd8dc99b2689 completed March 31, 2026, 10:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69cebbb11140819081bde8a1565aad4a completed April 2, 2026, 6:55 p.m.
Created at: March 30, 2026, 6:24 p.m.