Triple

T1328862
Position Surface form Disambiguated ID Type / Status
Subject Tifinagh E28394 entity
Predicate usedFor P98 FINISHED
Object Tamazight language E151658 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 language | Statement: [Tifinagh, usedFor, Tamazight language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tamazight language
Context triple: [Tifinagh, usedFor, Tamazight language]
  • A. Tashelhit
    Tashelhit is a variety of the Amazigh (Berber) language family spoken primarily in southwestern Morocco.
  • B. Berber languages
    The Berber languages are a group of closely related Afroasiatic languages traditionally spoken by the Indigenous Amazigh peoples of North Africa, particularly in countries such as Morocco, Algeria, Libya, and Tunisia.
  • C. Kabyle
    Kabyle is a major Northern Berber language spoken primarily in the Kabylie region of Algeria by the Kabyle people.
  • D. Central Atlas Tamazight chosen
    Central Atlas Tamazight is a Berber (Amazigh) language spoken primarily in Morocco’s central Atlas region, forming part of the Northern Berber language group.
  • E. Standard Moroccan Amazigh
    Standard Moroccan Amazigh is the standardized variety of the Amazigh (Berber) language used in Morocco for education, media, and official communication.
  • 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_69a498540a2481909e807a762280d3ba completed March 1, 2026, 7:49 p.m.
NER Named-entity recognition batch_69a4c1c30c948190afc6342b3dcda948 completed March 1, 2026, 10:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69acc62978c08190be285167cf579f9f completed March 8, 2026, 12:43 a.m.
Created at: March 1, 2026, 7:55 p.m.