Triple

T22738465
Position Surface form Disambiguated ID Type / Status
Subject Bangang dialect E562338 entity
Predicate instanceOf P0 FINISHED
Object regional variety of Ghomalaʼ language C46774 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 Ghomalaʼ language
Context triple: [Bangang dialect, instanceOf, regional variety of Ghomalaʼ language]
  • A. regional variety of Guna language
    A regional variety of the Guna language is a geographically or socially distinct form of Guna characterized by systematic differences in pronunciation, vocabulary, and sometimes grammar while remaining mutually intelligible with other Guna varieties.
  • B. Dargwa language variety
    A Dargwa language variety is a specific regional or social form of the Dargwa language, characterized by distinct phonological, lexical, and grammatical features within the broader Dargwa linguistic continuum.
  • C. Gumuz language variety
    A Gumuz language variety is a specific form or dialect of the Gumuz language, distinguished by its unique phonological, lexical, or grammatical features within the broader Gumuz linguistic continuum.
  • D. Gondi language variety
    A Gondi language variety is a specific regional or social form of the Gondi language, distinguished by its own characteristic phonological, lexical, and grammatical features within the broader Dravidian language continuum.
  • E. Luri language variety
    A Luri language variety is a specific regional or social form of the Luri language, distinguished by its own characteristic phonological, lexical, and grammatical features within the broader continuum of Southwestern Iranian dialects.
  • 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_69e245513a5c81908d5cb471b4fc429d completed April 17, 2026, 2:36 p.m.
Created at: April 17, 2026, 3:22 p.m.