Triple
T32899467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halich-Lutsk Karaim |
E841568
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Northwestern Kipchak language |
C3815
|
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: Northwestern Kipchak language Context triple: [Halich-Lutsk Karaim, instanceOf, Northwestern Kipchak language]
-
A.
Mongolic language
A Mongolic language is any member of a family of closely related languages spoken primarily in Mongolia, northern China, and surrounding regions, characterized by agglutinative morphology and subject–object–verb word order.
-
B.
Caspian language
A Caspian language is any of several closely related Northwestern Iranian languages spoken along the southern coast of the Caspian Sea, characterized by shared phonological and grammatical features distinct from standard Persian.
-
C.
Pamir language
The Pamir language is a group of Eastern Iranian languages spoken in the high-mountain Pamir region of Tajikistan, Afghanistan, and surrounding areas, characterized by significant diversity and archaic linguistic features.
-
D.
Kalenjin language
Kalenjin language is a group of closely related Southern Nilotic languages spoken primarily by the Kalenjin people in Kenya, known for their rich oral tradition and distinctive phonological features.
-
E.
Turkic language
chosen
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.
- 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.