Triple
T15427988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Íslendingasögur |
E369562
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Old Norse prose literature |
C20241
|
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 Norse prose literature Context triple: [Íslendingasögur, instanceOf, Old Norse prose literature]
-
A.
Old Frisian literature
Old Frisian literature comprises the body of written texts in the Old Frisian language, including legal codes, religious writings, and poetic fragments produced between roughly the 13th and 16th centuries in the Frisian-speaking regions along the North Sea coast.
-
B.
North Germanic literature
chosen
North Germanic literature encompasses the written and oral literary traditions produced in the North Germanic languages (such as Old Norse, Icelandic, Norwegian, Danish, and Swedish), from medieval sagas and eddas to modern prose and poetry.
-
C.
Old Norse poetry collection
A curated anthology of poetic works composed in Old Norse, typically preserving skaldic and Eddic verse along with contextual notes on language, mythology, and culture.
-
D.
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.
-
E.
Old English homiletic collection
An Old English homiletic collection is a compiled set of sermons and religious teachings written in Old English, intended for use in preaching, instruction, and devotional reading in early medieval England.
- 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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
Created at: April 10, 2026, 3:20 a.m.