Triple
T32209942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breviary of Aniane |
E822770
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Visigothic legal code |
C9503
|
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: Visigothic legal code Context triple: [Breviary of Aniane, instanceOf, Visigothic legal code]
-
A.
Sardinian legal code
A Sardinian legal code is a structured body of laws and regulations historically or currently governing social, economic, and political life in Sardinia, reflecting its unique cultural, linguistic, and institutional traditions.
-
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.
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.
-
D.
Napoleonic code
The Napoleonic Code is a comprehensive civil law code established under Napoleon in 1804 that standardized and modernized private law—such as property, contracts, and family relations—across France and later influenced legal systems worldwide.
-
E.
medieval legislation
chosen
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.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:37 a.m.