Triple

T5665696
Position Surface form Disambiguated ID Type / Status
Subject Old Frisian law codes E124851 entity
Predicate instanceOf P0 FINISHED
Object medieval legal text corpus C12841 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: medieval legal text corpus
Context triple: [Old Frisian law codes, instanceOf, medieval legal text corpus]
  • A. medieval legislation
    Medieval legislation encompasses the body of laws, decrees, and legal customs established by monarchs, feudal lords, and religious authorities in Europe during the Middle Ages to regulate social order, property, crime, and governance.
  • B. medieval law
    Medieval law is the body of legal customs, codes, and practices that governed social, economic, and political life in Europe during the Middle Ages, blending local traditions, feudal obligations, royal decrees, and canon (church) law.
  • C. jurisprudence corpus chosen
    A jurisprudence corpus is a structured collection of legal texts, such as statutes, case law, and scholarly writings, compiled for analysis, research, and reference in the study and practice of law.
  • 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 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.
  • 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_69c00828906881908966f270b8f130cf completed March 22, 2026, 3:18 p.m.
Created at: March 22, 2026, 3:43 p.m.