Triple
T26676743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banda-Banda |
E672477
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Banda language variety |
C8103
|
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: Banda language variety Context triple: [Banda-Banda, instanceOf, Banda language variety]
-
A.
Banda languages
chosen
Banda languages are a group of closely related Ubangian languages spoken primarily in the Central African Republic and neighboring regions, characterized by shared phonological and grammatical features.
-
B.
Mari language variety
A Mari language variety is a specific form or dialect of the Mari language, distinguished by its unique phonological, grammatical, and lexical features used by a particular Mari-speaking community.
-
C.
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.
-
D.
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.
-
E.
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.
- F. None of above.
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_69eecda13424819092b17942c4edf722 |
completed | April 27, 2026, 2:44 a.m. |
Created at: April 27, 2026, 3:16 a.m.