Triple
T24479055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anyin Bia |
E617314
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of the Anyin language |
C49059
|
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 Anyin language Context triple: [Anyin Bia, instanceOf, variety of the Anyin language]
-
A.
Yao language variety
A Yao language variety is a specific regional or social form of the Yao language, distinguished by its own characteristic phonological, lexical, and grammatical features within the broader Yao linguistic continuum.
-
B.
Yana language variety
Yana language variety refers to any of the related but distinct forms of the Yana language traditionally spoken by the Yana people of northern California, encompassing dialectal differences in phonology, vocabulary, and grammar.
-
C.
variety of Fang language
A variety of Fang language is a specific regional or social form of the Fang language distinguished by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Fang forms.
-
D.
variety of the Kaili language
A variety of the Kaili language is a distinct regional or social form of Kaili characterized by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Kaili forms.
-
E.
Kaili language variety
The Kaili language variety is a group of closely related Austronesian dialects spoken primarily in Central Sulawesi, Indonesia, characterized by shared grammatical structures but notable phonological and lexical differences between communities.
- 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_69e2d7f3ae788190b683394db15f220e |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:21 a.m.