Triple
T31054225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Compilation of the Laws of the Russian Empire |
E791351
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian legal document |
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 document Context triple: [Compilation of the Laws of the Russian Empire, instanceOf, Russian legal document]
-
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.
Soviet document
A Soviet document is an official or unofficial written record produced within the Soviet Union’s political, administrative, or social systems, reflecting its bureaucratic procedures, ideology, and historical context.
-
C.
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.
-
D.
Russian official
A Russian official is a government-appointed or elected individual who holds authority within the political, administrative, or bureaucratic structures of the Russian Federation.
-
E.
Brazilian legal document
A Brazilian legal document is an official written instrument, issued or recognized by Brazilian authorities, that records, regulates, or proves rights, obligations, or legal facts under Brazilian law.
- 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_69f224cb08908190ba71ad9aa87518ed |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9 p.m.