Triple
T22333447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pauline Laws of the Russian Empire |
E552081
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | dynastic legal code |
C46123
|
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: dynastic legal code Context triple: [Pauline Laws of the Russian Empire, instanceOf, dynastic legal code]
-
A.
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.
-
B.
Joseon dynasty law code
A Joseon dynasty law code is a comprehensive legal compilation that systematically codifies the administrative, civil, and criminal laws governing the Korean Joseon state and its Confucian 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.
Chinese legal code
A Chinese legal code is a systematically organized collection of laws and regulations that defines legal norms, rights, obligations, and penalties within a Chinese jurisdiction.
-
E.
Mongol law
Mongol law refers to the legal principles, customary practices, and codified regulations—most notably the Yassa—developed under the Mongol Empire to govern its diverse subjects, maintain military discipline, and ensure social order across vast conquered territories.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:43 p.m.