Triple
T5093994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruthwell Cross inscriptions |
E114822
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early medieval Christian text |
C17548
|
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: early medieval Christian text Context triple: [Ruthwell Cross inscriptions, instanceOf, early medieval Christian text]
-
A.
early Christian work
An early Christian work is a text or artifact produced by followers of Jesus in the first centuries CE that expresses, develops, or transmits emerging Christian beliefs, practices, and community life.
-
B.
Late Antique Christian
A Late Antique Christian is an adherent of Christianity living between roughly the 3rd and 8th centuries CE, shaped by the Roman Empire’s transformation, emerging Christian institutions, and evolving theological and cultural debates.
-
C.
early medieval period
The early medieval period is a historical era roughly spanning the 5th to the 10th centuries CE, marked by the transformation of the Roman world, the formation of new kingdoms, the spread of Christianity and Islam, and the gradual development of medieval European, Byzantine, and Islamic civilizations.
-
D.
5th-century text
A 5th-century text is a written work created or compiled between 401 and 500 CE, reflecting the linguistic, cultural, religious, and intellectual contexts of that historical period.
-
E.
medieval prose text
A medieval prose text is a written work from the Middle Ages composed in continuous, non-verse form, often preserving narratives, religious teachings, legal codes, or historical accounts in the vernacular or Latin.
- F. None of above. chosen
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.