Triple
T15829157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uruz Bey’in Esir Olduğu Boy |
E383822
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | story in the Book of Dede Korkut |
C19073
|
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: story in the Book of Dede Korkut Context triple: [Uruz Bey’in Esir Olduğu Boy, instanceOf, story in the Book of Dede Korkut]
-
A.
Turkic literature
chosen
Turkic literature encompasses the oral and written literary traditions produced in Turkic languages across Central Asia, Anatolia, the Caucasus, and surrounding regions, reflecting diverse historical, cultural, and religious influences.
-
B.
son of a khan
A "son of a khan" is a male offspring of a khan, often positioned as a noble heir with potential claims to leadership, power, and prestige within a khanate or tribal hierarchy.
-
C.
legendary narrative
A legendary narrative is a traditional story, often rooted in historical events or figures, that has been embellished over time with mythical or supernatural elements to convey cultural values or explain the extraordinary.
-
D.
Japanese historical tale
A Japanese historical tale is a narrative work that recounts and embellishes real past events, figures, and battles in Japan’s history, blending factual record with literary storytelling.
-
E.
Cambodian national epic
The Cambodian national epic is a foundational narrative poem or cycle of stories that embodies Cambodia’s cultural identity, history, values, and mythic heritage, often drawing on Hindu-Buddhist traditions and local legends.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:49 a.m.