Triple
T30801475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penal Code (1810) |
E784380
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Napoleonic code |
C57229
|
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: Napoleonic code Context triple: [Penal Code (1810), instanceOf, Napoleonic code]
-
A.
Napoleonic code
chosen
The Napoleonic Code is a comprehensive civil law code established under Napoleon in 1804 that standardized and modernized private law—such as property, contracts, and family relations—across France and later influenced legal systems worldwide.
-
B.
Prussian law
Prussian law refers to the body of legal principles, statutes, and judicial practices that governed the Kingdom of Prussia, characterized by a strong centralized authority, codification efforts like the Allgemeines Landrecht, and an emphasis on bureaucratic administration and social order.
-
C.
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.
-
D.
dynastic legal code
A dynastic legal code is a formalized set of laws and regulations established and enforced by a ruling dynasty to govern its subjects, institutions, and social order.
-
E.
colonial law code
A colonial law code is a formalized set of legal rules and procedures imposed by a colonial power to govern its territories and subjects, often blending metropolitan laws with local customs to maintain control and order.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:42 p.m.