Triple
T12658085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evenki language |
E302341
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Northern Tungusic language |
C16674
|
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: Northern Tungusic language Context triple: [Evenki language, instanceOf, Northern Tungusic language]
-
A.
Tungusic language
chosen
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.
-
B.
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.
-
C.
Uralic language
A Uralic language is a member of the Uralic language family, originating in Northern Eurasia and characterized by features such as agglutinative morphology, extensive case systems, and vowel harmony, including languages like Finnish, Hungarian, and Estonian.
-
D.
Northeast Caucasian language
A Northeast Caucasian language is a member of a diverse family of languages spoken primarily in the northeastern Caucasus region, characterized by complex consonant systems and rich case morphology.
-
E.
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.
- 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:19 p.m.