Triple
T37818656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilaqalpa dialect |
E942845
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of the Cupeño language |
C65026
|
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 Cupeño language Context triple: [Wilaqalpa dialect, instanceOf, variety of the Cupeño language]
-
A.
variety of the Luiseño language
A variety of the Luiseño language is a distinct regional or social form of Luiseño characterized by systematic differences in pronunciation, vocabulary, and/or grammar while remaining mutually intelligible with other Luiseño forms.
-
B.
Cahuilla language variety
Cahuilla language variety refers to any distinct regional or social form of the Cahuilla language, reflecting variations in pronunciation, vocabulary, and usage among Cahuilla-speaking communities.
-
C.
Yavapai language variety
A Yavapai language variety is a specific form or dialect of the Yavapai language, distinguished by unique phonological, lexical, or grammatical features used by a particular Yavapai-speaking community.
-
D.
Huavean language variety
A Huavean language variety is a specific linguistic form or dialect within the Huave (Wichí) language family, distinguished by its unique phonological, grammatical, and lexical features used by a particular Huave-speaking community.
-
E.
Kumeyaay dialect
A Kumeyaay dialect is a regional or community-specific variety of the Kumeyaay language, characterized by distinct phonological, lexical, and grammatical features within the broader Kumeyaay linguistic continuum.
- 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_69f76ee987588190906506e759be5db3 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.