Triple
T6903226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pandectae |
E159543
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Justinianic code |
C6981
|
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: Justinianic code Context triple: [Pandectae, instanceOf, Justinianic code]
-
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.
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.
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.
-
D.
Byzantine supplicatory canon
A Byzantine supplicatory canon is a structured liturgical hymn composed of multiple odes, chanted in the Eastern Christian tradition to implore divine mercy, aid, or intercession, often addressed to Christ, the Theotokos, or specific saints.
-
E.
part of the Corpus Juris Civilis
chosen
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.
- 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_69c6883822e0819091e321526f20ae0a |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:25 p.m.