Triple
T26215089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guana |
E655598
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of the Terena language |
C51261
|
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 Terena language Context triple: [Guana, instanceOf, variety of the Terena language]
-
A.
variety of the Tigre language
A variety of the Tigre language is a regional or social form of Tigre distinguished by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other forms.
-
B.
variety of the Uma language
A variety of the Uma language is a distinct regional or social form of Uma characterized by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other forms.
-
C.
Otomi language variety
An Otomi language variety is a specific regional or social form of the Otomi language, distinguished by its own phonological, lexical, and grammatical features within the broader Otomi linguistic continuum.
-
D.
variety of the Guna language
A variety of the Guna language is a distinct regional or social form of Guna characterized by systematic differences in pronunciation, vocabulary, and grammar while remaining mutually intelligible with other Guna forms.
-
E.
Rarámuri language variety
A Rarámuri language variety is a specific regional or social form of the Rarámuri (Tarahumara) language, distinguished by its unique phonological, lexical, and grammatical features within the broader Rarámuri 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
Created at: April 26, 2026, 8:54 p.m.