Triple
T223944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corpus Juris Civilis |
E4274
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman law codification |
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: Roman law codification Context triple: [Corpus Juris Civilis, instanceOf, Roman law codification]
-
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.
ancient civilization
An ancient civilization is a complex, organized society from antiquity characterized by urban development, social stratification, specialized labor, centralized governance, and enduring cultural, technological, and architectural achievements.
-
C.
British colonial law
British colonial law refers to the legal systems, statutes, and judicial practices imposed by Britain on its colonies, designed to maintain imperial control while selectively incorporating or reshaping local customs and institutions.
-
D.
Act of Congress
An Act of Congress is a formal law or statute enacted by the United States Congress and, typically upon receiving the President’s signature or a veto override, becomes legally binding federal legislation.
-
E.
colonial legislature
A colonial legislature is a representative governing body established in a colony to create laws, manage local affairs, and advise or balance the authority of the colonial governor and imperial power.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.