Triple
T24258354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Authenticum |
E604634
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | source for Roman law reception in Western Europe |
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: source for Roman law reception in Western Europe Context triple: [Authenticum, instanceOf, source for Roman law reception in Western Europe]
-
A.
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.
-
B.
Roman law scholar
A Roman law scholar is an expert who studies, interprets, and analyzes the legal systems, principles, and texts of ancient Rome and their influence on later legal traditions.
-
C.
commentator on Roman law
A commentator on Roman law is a legal scholar who analyzes, interprets, and explains the principles, texts, and historical applications of Roman legal systems.
-
D.
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.
-
E.
historical legal tradition
A historical legal tradition is a long-established system of laws, principles, and practices that has developed over time within a particular society or culture, shaping its legal institutions and norms.
- 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.