Triple
T24258447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De officio praefecti praetorio |
E604637
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman legal text |
C45442
|
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: ancient Roman legal text Context triple: [De officio praefecti praetorio, instanceOf, ancient Roman legal text]
-
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 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.
-
C.
Roman administrative text
chosen
A Roman administrative text is a written document produced by Roman authorities to record, regulate, or communicate matters of governance, such as laws, edicts, census data, tax records, and official correspondence.
-
D.
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.
-
E.
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.
- 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_69e29544c29c8190b023606eafe5d36a |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 18, 2026, 12:06 a.m.