Triple
T22324254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of the Eparch |
E551862
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine legal manual |
C6980
|
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 manual Context triple: [Book of the Eparch, instanceOf, Byzantine legal manual]
-
A.
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.
-
B.
late Roman legal codex
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.
-
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.
source of Byzantine law
chosen
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.
-
E.
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.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:42 p.m.