Triple
T32531048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Pame |
E831454
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Pame language variety |
C26530
|
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: Pame language variety Context triple: [Northern Pame, instanceOf, Pame language variety]
-
A.
Pame language
chosen
Pame language is a group of closely related Oto-Manguean indigenous languages spoken by the Pame people in the central highlands of Mexico, primarily in the state of San Luis Potosí.
-
B.
Mari language variety
A Mari language variety is a specific form or dialect of the Mari language, distinguished by its unique phonological, grammatical, and lexical features used by a particular Mari-speaking community.
-
C.
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.
-
D.
Subanen language variety
A Subanen language variety is a specific regional or social form of the Subanen language spoken by Subanen communities in the Zamboanga Peninsula and surrounding areas of the southern Philippines, characterized by distinct phonological, lexical, and grammatical features.
-
E.
Semai language variety
A Semai language variety is a specific form or dialect of the Semai language, distinguished by its unique phonological, lexical, or grammatical features used by a particular Semai-speaking community.
- 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:01 a.m.