Triple
T16951131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa María de Jesús Kaqchikel |
E411181
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kaqchikel language variety |
C38303
|
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: Kaqchikel language variety Context triple: [Santa María de Jesús Kaqchikel, instanceOf, Kaqchikel language variety]
-
A.
Mazatec language variety
A Mazatec language variety is a specific regional or social form of the Mazatec language, characterized by distinct phonological, lexical, and grammatical features within the broader Mazatecan linguistic continuum.
-
B.
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.
-
C.
Totonac language variety
A Totonac language variety is a specific regional or social form of the Totonac language, distinguished by its unique phonological, lexical, and grammatical features within the broader Totonacan language family.
-
D.
Cahuilla language variety
Cahuilla language variety refers to any distinct regional or social form of the Cahuilla language, reflecting variations in pronunciation, vocabulary, and usage among Cahuilla-speaking communities.
-
E.
Tepehua language variety
A Tepehua language variety is a specific regional or community-based form of the Tepehua language, distinguished by its own phonological, lexical, and grammatical features within the broader Totonacan language family.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:31 a.m.