Triple

T35423287
Position Surface form Disambiguated ID Type / Status
Subject Thaua (Tathra–Twofold Bay area) language E1023850 entity
Predicate instanceOf P0 FINISHED
Object Thaua language variety C63350 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: Thaua language variety
Context triple: [Thaua (Tathra–Twofold Bay area) language, instanceOf, Thaua language variety]
  • A. Rarámuri language variety
    A Rarámuri language variety is a specific regional or social form of the Rarámuri (Tarahumara) language, distinguished by its unique phonological, lexical, and grammatical features within the broader Rarámuri linguistic continuum.
  • B. Angas–Sura language variety
    The Angas–Sura language variety is a member of the Angas–Sura branch of the West Chadic languages, encompassing closely related dialects spoken primarily in central Nigeria.
  • C. Semai language variety
    A Semai language variety is a specific form or dialect of the Semai language, distinguished by its unique phonological, lexical, or grammatical features used by a particular Semai-speaking community.
  • D. Kunama language variety
    A Kunama language variety is a specific regional or social form of the Kunama language, distinguished by its own characteristic phonological, lexical, and grammatical features within the broader Kunama linguistic continuum.
  • E. Subanen language variety
    A Subanen language variety is a specific regional or social form of the Subanen language spoken by Subanen communities in the Zamboanga Peninsula and surrounding areas of the southern Philippines, characterized by distinct phonological, lexical, and grammatical features.
  • 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_69f76df6704081909900c60be10d5849 completed May 3, 2026, 3:47 p.m.
Created at: May 3, 2026, 4:03 p.m.