Triple
T21858216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yenisei inscriptions |
E539688
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Old Turkic inscriptions |
C18119
|
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 inscriptions Context triple: [Yenisei inscriptions, instanceOf, Old Turkic inscriptions]
-
A.
ancient inscriptions
chosen
Ancient inscriptions are texts or symbols carved, engraved, or written on durable materials such as stone, metal, or clay by past civilizations, serving as primary evidence of their language, culture, beliefs, and historical events.
-
B.
Turkic literature
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.
-
C.
Old Javanese inscription
An Old Javanese inscription is a historical text carved or written in the Old Javanese language, typically on stone, metal, or other durable materials, documenting political, religious, legal, or social matters in ancient Java.
-
D.
7th-century inscription
A 7th-century inscription is a text carved, engraved, or written on a durable material during the 600s CE, providing contemporary evidence of the language, culture, and historical events of that period.
-
E.
Russian inscription
A Russian inscription is a written text or engraving in the Russian language, typically using the Cyrillic alphabet, found on objects, monuments, documents, or surfaces to convey information, dedication, or identification.
- 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_69e0c47829648190bbe2d1d7033768ec |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 6:56 p.m.