Triple

T31116708
Position Surface form Disambiguated ID Type / Status
Subject Æthel E793108 entity
Predicate instanceOf P0 FINISHED
Object Old English lexeme C40611 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 lexeme
Context triple: [Æthel, instanceOf, Old English lexeme]
  • A. Old English term chosen
    An Old English term is a word or expression originating from the early medieval English language (circa 5th–11th centuries), often preserved in historical texts and studied for its linguistic and cultural significance.
  • B. Old English toponym
    An Old English toponym is a place-name whose form and meaning originate from the Old English language, often reflecting early medieval landscape features, settlements, or ownership.
  • C. 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.
  • D. 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.
  • E. 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.
  • 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_69f224d0a7688190af3fe3e6e26d01ed completed April 29, 2026, 3:33 p.m.
Created at: April 29, 2026, 9:04 p.m.