Triple

T6576357
Position Surface form Disambiguated ID Type / Status
Subject Humburi Senni language E155572 entity
Predicate hasLoanwordsFrom P506 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: [Humburi Senni language, hasLoanwordsFrom, Tamasheq]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tamasheq
Context triple: [Humburi Senni language, hasLoanwordsFrom, Tamasheq]
  • A. Tamasheq chosen
    Tamasheq is a Berber language spoken by the Tuareg people of the central Sahara region.
  • B. Tashelhit
    Tashelhit is a variety of the Amazigh (Berber) language family spoken primarily in southwestern Morocco.
  • C. ትግርኛ
    ትግርኛ is a Semitic language primarily spoken in Eritrea and northern Ethiopia by the Tigrinya people.
  • D. Badaga language
    Badaga language is a Southern Dravidian language spoken primarily by the Badaga community in the Nilgiri Hills of Tamil Nadu, India.
  • E. Kanuri
    The Kanuri are a major ethnic group of the central Sahara and Lake Chad region, historically associated with the Kanem-Bornu Empire and known for their distinct language and Islamic cultural heritage.
  • 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_69c688151254819080387f87deab8fa7 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6ae7399488190b5f6948c60188aec completed March 27, 2026, 4:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6e42945348190882e6ffd05977d36 completed March 27, 2026, 8:10 p.m.
Created at: March 27, 2026, 1:54 p.m.