Triple
T37047753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Sisaala |
E916963
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sisaala language variety |
C29516
|
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: Sisaala language variety Context triple: [Western Sisaala, instanceOf, Sisaala language variety]
-
A.
Sisaala language dialect
chosen
A Sisaala language dialect is a regional or community-specific variety of the Sisaala language, distinguished by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Sisaala varieties.
-
B.
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.
-
C.
Ixil language variety
Ixil language variety refers to any of the closely related Mayan language forms spoken by the Ixil people, typically distinguished by regional, phonological, or lexical differences within the broader Ixil language.
-
D.
Luri language variety
A Luri language variety is a specific regional or social form of the Luri language, distinguished by its own characteristic phonological, lexical, and grammatical features within the broader continuum of Southwestern Iranian dialects.
-
E.
Hlai language variety
A Hlai language variety is a specific regional or social form of the Hlai language, distinguished by its own phonological, lexical, and grammatical features within the broader Hlai 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_69f76e94d0308190a3f06890e133c88e |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.