Triple
T24849757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jesuit Law of 1872 |
E621853
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German imperial 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: German imperial law Context triple: [Jesuit Law of 1872, instanceOf, German imperial law]
-
A.
Prussian law
chosen
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.
-
B.
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.
-
C.
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.
-
D.
Austrian federal law
Austrian federal law is the body of legal norms enacted at the national level in Austria that governs matters within the competence of the federal state, such as constitutional structure, civil and criminal law, and nationwide administrative regulations.
-
E.
Japanese imperial law
Japanese imperial law is the body of legal principles, statutes, and institutional practices that governed the authority, succession, and functions of the Emperor and imperial household within Japan’s historical and constitutional frameworks.
- 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_69e2fac297e481909d3aedc75f585e42 |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 5:20 a.m.