Triple
T16760819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tin-Essako |
E407337
|
entity |
| Predicate | localLanguages |
P10892
|
FINISHED |
| Object | Tamasheq |
E203666
|
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: Tamasheq | Statement: [Tin-Essako, localLanguages, Tamasheq]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tamasheq Context triple: [Tin-Essako, localLanguages, Tamasheq]
-
A.
Tamasheq
chosen
Tamasheq is a Berber language spoken by the Tuareg people of the central Sahara region.
-
B.
Koyraboro Senni language
The Koyraboro Senni language is a Songhay language spoken primarily along the Niger River in Mali, notably around the city of Gao.
-
C.
Tashelhit
Tashelhit is a variety of the Amazigh (Berber) language family spoken primarily in southwestern Morocco.
-
D.
N’Ko
N’Ko is a writing system devised in the 20th century for Manding languages of West Africa, notable for its right-to-left script and role in promoting literacy and cultural identity.
-
E.
ትግርኛ
ትግርኛ is a Semitic language primarily spoken in Eritrea and northern Ethiopia by the Tigrinya people.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3abec638c81909d71ff452a4123c9 |
completed | April 18, 2026, 4:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00a52d077081908080c61da67e0032 |
completed | May 10, 2026, 3:33 p.m. |
Created at: April 10, 2026, 5:21 a.m.