Triple
T14661139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guna of Wargandí |
E344239
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of Guna language |
C35196
|
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 Guna language Context triple: [Guna of Wargandí, instanceOf, regional variety of Guna language]
-
A.
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.
-
B.
Amuzgo language variety
An Amuzgo language variety is a specific regional or social form of the Amuzgo language, distinguished by its unique phonological, lexical, and grammatical features within the broader Amuzgo linguistic continuum.
-
C.
Mazatec language variety
A Mazatec language variety is a specific regional or social form of the Mazatec language, characterized by distinct phonological, lexical, and grammatical features within the broader Mazatecan linguistic continuum.
-
D.
Tepehua language variety
A Tepehua language variety is a specific regional or community-based form of the Tepehua language, distinguished by its own phonological, lexical, and grammatical features within the broader Totonacan language family.
-
E.
Ivatan language variety
A specific form or dialect of the Ivatan language, characterized by its unique phonological, lexical, and grammatical features within the Ivatan-speaking community.
- 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:27 a.m.