Triple
T24407904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senchus fer n-Alban |
E615362
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Gaelic text |
C37219
|
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: medieval Gaelic text Context triple: [Senchus fer n-Alban, instanceOf, medieval Gaelic text]
-
A.
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.
-
B.
medieval Icelandic manuscript
A medieval Icelandic manuscript is a handwritten document, typically on vellum, preserving Old Norse literary, legal, historical, or religious texts produced in Iceland between the 12th and 16th centuries.
-
C.
Gothic-language text
A Gothic-language text is any written work composed in the extinct East Germanic language Gothic, typically preserved in manuscripts such as biblical translations and legal or liturgical documents from the early medieval period.
-
D.
early medieval Christian text
An early medieval Christian text is a written work produced roughly between the 5th and 11th centuries that reflects and shapes Christian theology, liturgy, devotion, or ecclesiastical practice within the cultural and political contexts of early medieval Europe and the Mediterranean.
-
E.
Scottish chronicle
chosen
A Scottish chronicle is a historical narrative or record that details events, rulers, and significant occurrences in Scotland’s past, often compiled by contemporary or near-contemporary writers.
- 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_69e2d7e780bc81908049c779e697a7f6 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:05 a.m.