Triple
T16291237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sobornoye Ulozheniye |
E395526
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian legal code |
C2138
|
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: Russian legal code Context triple: [Sobornoye Ulozheniye, instanceOf, Russian legal code]
-
A.
Russian federal law
A Russian federal law is a legally binding normative act adopted by the Federal Assembly and signed by the President of Russia, regulating key areas of public and private life across the entire Russian Federation.
-
B.
Russian imperial law
chosen
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.
Romanian law
Romanian law is the national legal system of Romania, based primarily on civil law traditions, that regulates the rights, obligations, and interactions of individuals, organizations, and public authorities within the Romanian state.
-
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.
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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:05 a.m.