Triple

T6497157
Position Surface form Disambiguated ID Type / Status
Subject Typos of Constans II E148786 entity
Predicate instanceOf P0 FINISHED
Object Byzantine legal document C6479 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: Byzantine legal document
Context triple: [Typos of Constans II, instanceOf, Byzantine legal document]
  • A. Byzantine law code chosen
    A Byzantine law code is a systematically organized collection of legal rules, imperial edicts, and judicial interpretations that governed civil, criminal, and ecclesiastical matters in the Byzantine Empire.
  • B. source of Byzantine law
    A source of Byzantine law is any authoritative origin—such as imperial legislation, ecclesiastical canons, juristic writings, or customary practices—from which the legal norms of the Byzantine Empire were derived and recognized.
  • C. part of the Corpus Juris Civilis
    A part of the Corpus Juris Civilis is a distinct component (such as the Code, Digest, Institutes, or Novels) of the comprehensive body of Roman civil law compiled under Emperor Justinian I.
  • D. Byzantine jurist
    A Byzantine jurist is a legal scholar or judge of the Byzantine Empire who interpreted, applied, and commented on Roman and Byzantine law within the empire’s complex religious and imperial framework.
  • E. Byzantine chronicle
    A Byzantine chronicle is a historical narrative, often arranged annalistically, that records events of the Byzantine Empire and surrounding regions, typically blending factual reporting with religious interpretation and classical traditions.
  • 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_69c687e9ad288190bae5bcac9c8ac855 completed March 27, 2026, 1:36 p.m.
Created at: March 27, 2026, 1:41 p.m.