Triple
T11889507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nīhithawīwin |
E282877
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cree language variety |
C15457
|
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: Cree language variety Context triple: [Nīhithawīwin, instanceOf, Cree 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.
Indigenous language variety of Canada
chosen
An Indigenous language variety of Canada is a distinct linguistic system or dialect traditionally spoken by First Nations, Inuit, or Métis communities within the territory now known as Canada, reflecting unique cultural, historical, and geographic identities.
-
C.
Yup'ik language variety
A Yup'ik language variety is a specific regional or social form of the Yup'ik language distinguished by its unique phonological, lexical, and grammatical features within the broader Yup'ik linguistic continuum.
-
D.
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.
-
E.
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.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:44 p.m.