Triple

T38622221
Position Surface form Disambiguated ID Type / Status
Subject Southern Tumbuka E936901 entity
Predicate instanceOf P0 FINISHED
Object regional variety of Tumbuka C62851 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 Tumbuka
Context triple: [Southern Tumbuka, instanceOf, regional variety of Tumbuka]
  • A. Tumbuka language chosen
    Tumbuka language is a Bantu language spoken primarily in northern Malawi and parts of Zambia and Tanzania, known for its rich noun class system and tonal distinctions.
  • B. Makhuwa language variety
    A Makhuwa language variety is a specific regional or social form of the Makhuwa Bantu language, distinguished by its own phonological, lexical, or grammatical features within the broader Makhuwa linguistic continuum.
  • C. Tswa–Ronga language variety
    A Tswa–Ronga language variety is a specific regional or social form of the Tswa–Ronga language cluster, characterized by distinct phonological, lexical, and grammatical features shared by its speakers.
  • D. regional variety of Kikuyu language
    A regional variety of the Kikuyu language is a geographically defined form of Kikuyu characterized by distinct phonological, lexical, and sometimes grammatical features shared by speakers in a particular area.
  • E. regional variety of siSwati
    A regional variety of siSwati is a geographically or socially localized form of the siSwati language characterized by distinct pronunciation, vocabulary, and sometimes grammar that differentiate it from other siSwati varieties.
  • 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_69f76ed403208190b862dc795171353f completed May 3, 2026, 3:50 p.m.
Created at: May 3, 2026, 4:32 p.m.