Triple
T34359436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koblandy Batyr |
E881830
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | figure of Kazakh mythology |
C3096
|
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: figure of Kazakh mythology Context triple: [Koblandy Batyr, instanceOf, figure of Kazakh mythology]
-
A.
Turkic deity
A Turkic deity is a divine being from the mythologies of Turkic peoples, embodying natural forces, social values, or cosmic principles within their traditional belief systems.
-
B.
mythological figure
chosen
A mythological figure is a legendary being or character from traditional stories and belief systems, often embodying cultural values, natural forces, or supernatural powers.
-
C.
component of Kazakh zhuzes
A component of Kazakh zhuzes is a structural subdivision within one of the three traditional Kazakh tribal confederations (Senior, Middle, or Junior zhuz), representing a specific tribal or clan grouping with shared ancestry and territorial ties.
-
D.
Mongolic deity
A Mongolic deity is a supernatural being revered in Mongolic religious traditions, often associated with natural forces, ancestral spirits, or protective roles within nomadic life.
-
E.
character in Estonian mythology
A character in Estonian mythology is a mythic figure—such as a deity, spirit, hero, or supernatural being—embodying natural forces, moral values, or cultural ideals within Estonia’s traditional folklore and belief systems.
- 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_69f349be5c9c81908dc726ae1f4c68f2 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:58 a.m.