Triple
T32899466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halich-Lutsk Karaim |
E841568
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kipchak Turkic language variety |
C7978
|
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: Kipchak Turkic language variety Context triple: [Halich-Lutsk Karaim, instanceOf, Kipchak Turkic language variety]
-
A.
Turkic language
A Turkic language is a member of a family of closely related languages spoken across a vast area from Eastern Europe and Anatolia through Central Asia to Siberia and Western China, characterized by agglutinative morphology, vowel harmony, and similar grammatical structures.
-
B.
branch of the Turkic languages
chosen
A branch of the Turkic languages is a subgroup of related Turkic languages that share a common historical origin, structural features, and vocabulary within the broader Turkic language family.
-
C.
Turkic–Iranian mixed language
A Turkic–Iranian mixed language is a contact language that combines core grammatical and lexical features from both Turkic and Iranian language families, typically arising in regions where their speaker communities have long coexisted.
-
D.
Turkic word
A Turkic word is a lexical item belonging to the Turkic language family, characterized by agglutinative morphology, vowel harmony, and shared historical roots across related languages.
-
E.
Tungusic language
A Tungusic language is a member of a small family of agglutinative languages spoken primarily in eastern Siberia, northeastern China, and the Russian Far East by Tungusic peoples.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:19 a.m.