Triple
T5665699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Frisian law codes |
E124851
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Old Frisian literature |
C18551
|
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 Frisian literature Context triple: [Old Frisian law codes, instanceOf, Old Frisian literature]
-
A.
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.
-
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 High German poem
An Old High German poem is a verse composition written in the Old High German language (c. 750–1050 CE), typically preserved in medieval manuscripts and reflecting early Germanic culture, Christianization, and poetic traditions.
-
E.
Old English religious text
An Old English religious text is a written work composed in the Old English language that conveys Christian doctrines, biblical narratives, liturgical materials, or moral teachings for spiritual instruction and devotion in early medieval England.
- 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_69c00828906881908966f270b8f130cf |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:43 p.m.