Triple
T7406821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breviary of Alaric |
E170891
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | late Roman legal compilation |
C21348
|
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: late Roman legal compilation Context triple: [Breviary of Alaric, instanceOf, late Roman legal compilation]
-
A.
late Roman legal codex
chosen
A late Roman legal codex is a formally compiled, systematically organized collection of imperial laws, juristic writings, and legal principles produced in the later Roman Empire to standardize and preserve authoritative legal practice.
-
B.
Byzantine law code
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.
-
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.
early modern legal codification
Early modern legal codification is the systematic collection, organization, and formal enactment of laws in comprehensive written codes by emerging centralized states between roughly the 16th and 18th centuries.
-
E.
Roman law textbook
A Roman law textbook is a comprehensive instructional volume that explains the principles, institutions, procedures, and historical development of Roman legal systems, often with translations, commentary, and case analyses.
- 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_69c68a6010108190925e5284de022660 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:10 p.m.