Triple
T23122948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tgdaya Seediq |
E576949
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of the Seediq language |
C47254
|
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 Seediq language Context triple: [Tgdaya Seediq, instanceOf, variety of the Seediq language]
-
A.
variety of the Zhuang language
A variety of the Zhuang language is a distinct regional or social form of Zhuang characterized by its own phonological, lexical, and grammatical features while remaining mutually intelligible to varying degrees with other Zhuang varieties.
-
B.
Zhuang language variety
A Zhuang language variety is a specific regional or social form of the Zhuang language, characterized by distinct phonological, lexical, and grammatical features within the broader Tai language continuum.
-
C.
variety of the Guna language
A variety of the Guna language is a distinct regional or social form of Guna characterized by systematic differences in pronunciation, vocabulary, and grammar while remaining mutually intelligible with other Guna forms.
-
D.
variety of the Naxi language
A variety of the Naxi language is a regional or social form of Naxi distinguished by systematic differences in pronunciation, vocabulary, and sometimes grammar while remaining mutually intelligible with other Naxi forms.
-
E.
variety of the Dinka language
A variety of the Dinka language is a specific regional or social form of Dinka distinguished by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Dinka varieties.
- 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_69e245f6c2e881909a228fdcfeb7c7d3 |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 3:59 p.m.