Triple
T185651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman law |
E3974
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical legal system |
C820
|
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: historical legal system Context triple: [Roman law, instanceOf, historical legal system]
-
A.
civil law tradition
chosen
The civil law tradition is a legal system rooted in comprehensive written codes and statutes, derived primarily from Roman law, in which judges apply and interpret codified rules rather than relying heavily on judicial precedent.
-
B.
mixed legal system
A mixed legal system is a national legal framework that combines elements from two or more major legal traditions—such as civil law, common law, religious law, or customary law—into a single, functioning system.
-
C.
legal doctrine
A legal doctrine is a principle or framework developed through statutes, judicial decisions, and scholarly interpretation that guides how laws are understood, applied, and evolved in legal systems.
-
D.
historical period
A historical period is a span of time characterized by distinct social, political, cultural, or technological conditions that differentiate it from other eras in history.
-
E.
historical relationship
A historical relationship is a connection between people, groups, or entities that existed in the past and is understood through documented events, interactions, and their lasting impact over time.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.