Triple
T32899468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halich-Lutsk Karaim |
E841568
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Karaim language variety |
C58896
|
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: Karaim language variety Context triple: [Halich-Lutsk Karaim, instanceOf, Karaim language variety]
-
A.
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.
-
B.
Dargwa language variety
A Dargwa language variety is a specific regional or social form of the Dargwa language, characterized by distinct phonological, lexical, and grammatical features within the broader Dargwa linguistic continuum.
-
C.
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.
-
D.
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.
-
E.
Sabaic language variety
A Sabaic language variety is a specific form or dialect of the ancient South Arabian Sabaic language, distinguished by its unique linguistic features, geographic distribution, and historical context within the Sabaean cultural sphere.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:19 a.m.