Triple
T30377093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irapa Yukpa |
E772720
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of Yukpa |
C56833
|
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 Yukpa Context triple: [Irapa Yukpa, instanceOf, regional variety of Yukpa]
-
A.
Yokutsan language variety
A Yokutsan language variety is a specific linguistic form or dialect within the Yokutsan language family traditionally spoken by Indigenous Yokuts peoples of California’s Central Valley.
-
B.
Kaqchikel language variety
The Kaqchikel language variety is a Mayan language spoken primarily in the central highlands of Guatemala, characterized by its agglutinative morphology, ergative-absolutive alignment, and rich system of aspect and status markers.
-
C.
regional variety of Guna language
A regional variety of the Guna language is a geographically or socially distinct form of Guna characterized by systematic differences in pronunciation, vocabulary, and sometimes grammar while remaining mutually intelligible with other Guna varieties.
-
D.
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.
-
E.
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.
- 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_69f2248e3444819081b05712dc6873de |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8 p.m.