Triple
T25041311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yabula Yabula language |
E627119
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Yorta Yorta language variety |
C49373
|
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: Yorta Yorta language variety Context triple: [Yabula Yabula language, instanceOf, Yorta Yorta language variety]
-
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.
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.
-
C.
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.
-
D.
Luri language variety
A Luri language variety is a specific regional or social form of the Luri language, distinguished by its own characteristic phonological, lexical, and grammatical features within the broader continuum of Southwestern Iranian dialects.
-
E.
Dargwa language variety
A Dargwa language variety is a specific regional or social form of the Dargwa language, characterized by distinct phonological, lexical, and grammatical features within the broader Dargwa 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_69e2ff2b4c80819087c916b2b16241b9 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:08 a.m.