Triple

T5094652
Position Surface form Disambiguated ID Type / Status
Subject Old English homilies E114837 entity
Predicate instanceOf P0 FINISHED
Object Old English literature C12780 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 English literature
Context triple: [Old English homilies, instanceOf, Old English literature]
  • A. Old English writer
    An Old English writer is an author who composed literary, religious, or historical texts in the Old English language during the early medieval period in England.
  • B. Anglo-Saxon
    Anglo-Saxon refers to the early medieval Germanic peoples from present-day Germany and Denmark who settled in England from the 5th century onward, as well as their language, culture, and societal structures.
  • C. Middle English narrative poem
    A Middle English narrative poem is a verse composition written in the Middle English language that tells a structured story, often involving adventure, romance, morality, or religious themes.
  • D. Anglo-Norman manuscript tradition
    The Anglo-Norman manuscript tradition encompasses the body of texts written in Anglo-Norman French in medieval England, preserved and transmitted through manuscripts that reflect the linguistic, cultural, and political interplay between Norman and English societies from the 11th to the 15th centuries.
  • E. medieval literary work chosen
    A medieval literary work is a written or orally transmitted text from roughly the 5th to the 15th century that reflects the cultural, religious, and social contexts of the Middle Ages through genres such as epics, romances, hagiographies, chronicles, and lyric poetry.
  • 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_69bd443fc49c819089629c00e311310c completed March 20, 2026, 12:57 p.m.
Created at: March 20, 2026, 1:40 p.m.