Triple
T21666113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aritao Isinay |
E534720
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of the Isinay language |
C45143
|
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 Isinay language Context triple: [Aritao Isinay, instanceOf, variety of the Isinay 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.
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.
-
C.
Visayan language variety
A Visayan language variety is a specific regional or social form of any language within the Visayan (Bisayan) subgroup of the Austronesian language family, characterized by distinct phonological, lexical, and grammatical features.
-
D.
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.
-
E.
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.
- 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_69e0c467e1f48190af2650b19175abc4 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:36 p.m.