Triple
T9669744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orkhon inscriptions |
E233995
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Old Turkic text |
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: Old Turkic text Context triple: [Orkhon inscriptions, instanceOf, Old Turkic text]
-
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.
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.
-
C.
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.
-
D.
Middle Persian text
A Middle Persian text is a written work composed in the Middle Iranian language of the Sasanian and early Islamic periods, typically preserved in Pahlavi script or related writing systems.
-
E.
Turkic person
A Turkic person is an individual who identifies with or descends from the diverse ethnolinguistic groups that speak Turkic languages and share related historical and cultural traditions across Eurasia.
- 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:15 p.m.