Triple
T28773325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Senate decree of 32 BCE |
E726469
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman legal act |
C54574
|
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: Roman legal act Context triple: [Roman Senate decree of 32 BCE, instanceOf, Roman legal act]
-
A.
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.
-
B.
Roman state formula
chosen
A Roman state formula is a standardized legal or ceremonial expression used in official Roman documents and rituals to articulate the authority, structure, and obligations of the Roman state.
-
C.
Roman jurist
A Roman jurist was a legal expert in ancient Rome who interpreted, developed, and advised on Roman law, shaping its doctrines and practical application.
-
D.
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.
-
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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:16 a.m.