Triple
T2787013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 Russian time zone reform |
E61835
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | law of Russia |
C2055
|
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: law of Russia Context triple: [2014 Russian time zone reform, instanceOf, law of Russia]
-
A.
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.
-
B.
law
chosen
Law is a system of rules and principles, enforced by social or governmental institutions, that regulates behavior and resolves disputes within a society.
-
C.
system of laws
A system of laws is an organized and coherent set of rules and principles established by an authority to regulate behavior, resolve disputes, and maintain order within a society.
-
D.
republic of Russia
The Republic of Russia is a conceptual class representing a sovereign, federated state characterized by a republican form of government, centralized authority, and a diverse composition of regions and peoples within its political and legal framework.
-
E.
federal subject of Russia
A federal subject of Russia is a top-level administrative and political division of the Russian Federation, such as an oblast, republic, krai, autonomous okrug, federal city, or autonomous oblast, each with its own degree of autonomy and representation in federal institutions.
- 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_69ab4b7f51d881908768300ebd2fbdae |
completed | March 6, 2026, 9:47 p.m. |
Created at: March 6, 2026, 9:57 p.m.