Triple

T13554080
Position Surface form Disambiguated ID Type / Status
Subject Padang Dinka E323724 entity
Predicate instanceOf P0 FINISHED
Object variety of the Dinka language C33208 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: variety of the Dinka language
Context triple: [Padang Dinka, instanceOf, variety of the Dinka language]
  • A. variety of the Nuer language
    A variety of the Nuer language is a distinct regional or social form of Nuer characterized by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other Nuer forms.
  • 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. Akan language variety
    A specific form or dialect of the Akan language, distinguished by its unique phonological, lexical, and grammatical features used by a particular regional or social group.
  • D. Songhay language variety
    A Songhay language variety is a specific regional or social form of the Songhay language continuum, distinguished by its unique phonological, lexical, and grammatical features while remaining mutually intelligible to varying degrees with other Songhay varieties.
  • E. Nilotic languages branch
    The Nilotic languages branch is a group of related languages spoken primarily along the Nile Valley and surrounding regions of East Africa, including parts of South Sudan, Uganda, Kenya, Tanzania, and Ethiopia.
  • F. None of above. chosen

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_69d8076830b48190910a902bae5888e2 completed April 9, 2026, 8:09 p.m.
Created at: April 9, 2026, 9:46 p.m.