Triple
T15149447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Háttatal |
E361897
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Old Norse poetic treatise |
C12781
|
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 poetic treatise Context triple: [Háttatal, instanceOf, Old Norse poetic treatise]
-
A.
Old Norse poetry collection
chosen
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.
-
B.
Old English literary work
An Old English literary work is a written composition created in the Old English language (c. 5th–11th centuries), encompassing genres such as poetry, prose, and religious or historical texts that reflect the culture and society of early medieval England.
-
C.
Anglo-Saxon literary collection
An Anglo-Saxon literary collection is an organized compilation of texts, poems, homilies, and other writings produced in or about the Anglo-Saxon period, typically preserved in manuscript form for study and reference.
-
D.
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.
-
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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:07 a.m.