Triple
T19601341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prussian Edict of Emancipation of 1812 |
E470483
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Prussian law |
C42252
|
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: Prussian law Context triple: [Prussian Edict of Emancipation of 1812, instanceOf, Prussian law]
-
A.
German federal statute
A German federal statute is a legally binding rule enacted by the federal legislature of Germany that applies uniformly across all federal states.
-
B.
Russian imperial law
Russian imperial law was the evolving body of statutes, decrees, and legal principles that governed the Russian Empire from the early tsarist period through 1917, reflecting autocratic authority, codified reforms, and complex interactions among imperial, regional, and customary norms.
-
C.
Dutch statute
A Dutch statute is a formal written law enacted by the Dutch legislature (Staten-Generaal) and, where required, sanctioned and promulgated by the government, forming part of the binding legal framework of the Netherlands.
-
D.
barbarian law code
A barbarian law code is a written compilation of legal customs and rules created by early medieval Germanic or other so‑called “barbarian” peoples, often blending tribal traditions with Roman legal influences.
-
E.
Prussian royal
A Prussian royal is a member of the ruling Hohenzollern dynasty or its close relatives who held hereditary titles and exercised or symbolized monarchical authority in the Kingdom of Prussia.
- F. None of above. chosen
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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
Created at: April 10, 2026, 1:43 p.m.