Triple
T5242003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khenifra |
E118364
|
entity |
| Predicate | hasEthnicGroup |
P1898
|
FINISHED |
| Object | Amazigh |
E207468
|
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: Amazigh | Statement: [Khenifra, hasEthnicGroup, Amazigh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amazigh Context triple: [Khenifra, hasEthnicGroup, Amazigh]
-
A.
Amazigh
chosen
Amazigh are the Indigenous Berber peoples of North Africa, known for their distinct languages, culture, and historical presence across the Maghreb and Sahara regions.
-
B.
Kabyle
Kabyle is a major Northern Berber language spoken primarily in the Kabylie region of Algeria by the Kabyle people.
-
C.
Mozabite Berber
Mozabite Berber is a Zenati Berber language spoken primarily by the Ibadi Mozabite community in Algeria’s M’zab region.
-
D.
Riffian Berber
Riffian Berber is a Northern Berber language spoken primarily by the Riffian people in the Rif region of northern Morocco.
-
E.
Tashelhit
Tashelhit is a variety of the Amazigh (Berber) language family spoken primarily in southwestern Morocco.
- 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_69bd4467db0881909b3b0982df32cc8f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b4c6fa8819099442b1b110e51fb |
completed | March 20, 2026, 4:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69befe65e3048190899a6316dc4c89eb |
completed | March 21, 2026, 8:24 p.m. |
Created at: March 20, 2026, 1:49 p.m.