Triple

T24479105
Position Surface form Disambiguated ID Type / Status
Subject Asabu dialect E617316 entity
Predicate instanceOf P0 FINISHED
Object regional variety of Baoulé language C7393 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: regional variety of Baoulé language
Context triple: [Asabu dialect, instanceOf, regional variety of Baoulé language]
  • A. regional variety of the Nupe language
    A regional variety of the Nupe language is a geographically or socially defined form of Nupe that exhibits distinct phonological, lexical, or grammatical features while remaining mutually intelligible with other Nupe varieties.
  • B. Fula language variety
    A Fula language variety is a specific regional or social form of the Fula (Fulfulde/Pulaar/Pular) language distinguished by its phonological, lexical, and grammatical features within the broader Fula continuum.
  • C. Mande language chosen
    A Mande language is a member of a branch of the Niger-Congo language family spoken primarily in West Africa, characterized by tonal systems, isolating morphology, and a shared historical origin among its diverse regional varieties.
  • D. Volta–Niger language
    A Volta–Niger language is a member of a proposed branch of the Niger–Congo language family spoken primarily in southern Nigeria and neighboring regions, characterized by significant lexical and grammatical diversity among its constituent languages.
  • E. variety of the Duala language
    A variety of the Duala language is a regional or social form of Duala distinguished by specific phonological, lexical, or grammatical features while remaining mutually intelligible with other Duala forms.
  • F. None of above.

Provenance (1 batch)

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_69e2d7f3ae788190b683394db15f220e completed April 18, 2026, 1:01 a.m.
Created at: April 18, 2026, 2:21 a.m.