Triple
T18029943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evenki culture |
E431358
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tungusic culture |
C16838
|
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: Tungusic culture Context triple: [Evenki culture, instanceOf, Tungusic culture]
-
A.
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.
-
B.
Indigenous peoples of the Russian Far East
chosen
Indigenous peoples of the Russian Far East are the diverse, historically rooted ethnic groups native to the northeastern regions of Russia, each with distinct languages, cultures, and traditional ways of life closely tied to the Arctic, subarctic, and Pacific environments.
-
C.
Pontic–Caspian steppe culture
The Pontic–Caspian steppe culture refers to the prehistoric and early historic societies that inhabited the vast grasslands north of the Black and Caspian Seas, often associated with early Indo-European migrations, pastoral nomadism, and kurgan burial traditions.
-
D.
Chukotko-Kamchatkan language
A Chukotko-Kamchatkan language is a member of a small family of indigenous languages spoken in northeastern Siberia, characterized by complex morphology and polysynthetic structure.
-
E.
Ossetian cultural tradition
Ossetian cultural tradition encompasses the customs, rituals, language, folklore, and social practices of the Ossetian people, shaped by their Caucasian heritage, Iranian roots, and Orthodox Christian and folk religious influences.
- 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_69d8b9050fb48190890155145deb0a66 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:25 a.m.