Triple
T21858217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yenisei inscriptions |
E539688
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | runic inscriptions |
C35438
|
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: runic inscriptions Context triple: [Yenisei inscriptions, instanceOf, runic inscriptions]
-
A.
ancient inscriptions
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.
runic character
chosen
A runic character is a symbolic glyph from ancient runic alphabets used primarily by Germanic peoples for writing, magic, and divination.
-
C.
religious inscription
A religious inscription is a text carved, written, or otherwise permanently recorded on a durable surface that conveys sacred messages, prayers, dedications, or doctrinal statements associated with a particular faith tradition.
-
D.
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.
-
E.
Hebrew inscription
A Hebrew inscription is a text carved, written, or engraved in the Hebrew language and script on a durable surface such as stone, metal, pottery, or parchment, often serving religious, commemorative, legal, or decorative purposes.
- 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.