Triple
T5093995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruthwell Cross inscriptions |
E114822
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | runic inscription |
C12549
|
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 inscription Context triple: [Ruthwell Cross inscriptions, instanceOf, runic inscription]
-
A.
multilingual inscription
A multilingual inscription is a written text or engraving that presents the same or related content in two or more languages, often to communicate across linguistic groups or preserve information for diverse audiences.
-
B.
Latin inscription
A Latin inscription is a text carved, engraved, or otherwise permanently marked in the Latin language on durable materials such as stone, metal, or pottery, typically serving commemorative, dedicatory, legal, or informational purposes.
-
C.
Etruscan inscription
An Etruscan inscription is a text written in the ancient Etruscan language, typically carved or painted on durable materials such as stone, metal, or pottery, providing evidence of the culture, religion, and daily life of the Etruscan civilization.
-
D.
epigraphic language
chosen
An epigraphic language is a language known primarily or exclusively from inscriptions carved or written on durable materials such as stone, metal, or pottery, rather than from extensive literary or manuscript traditions.
-
E.
Oscan inscription
An Oscan inscription is a written text in the Oscan language, typically carved on stone, metal, or pottery by ancient Italic peoples, providing evidence of their language, culture, and public or religious life.
- 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_69bd443fc49c819089629c00e311310c |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:40 p.m.