Triple
T5321894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russification of Finland |
E121693
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | policy of the Russian Empire |
C1297
|
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: policy of the Russian Empire Context triple: [Russification of Finland, instanceOf, policy of the Russian Empire]
-
A.
policy of the Soviet Union
The policy of the Soviet Union encompasses the ideological, political, economic, and foreign strategies implemented by the Soviet state to build and maintain a socialist system under one-party rule from 1917 to 1991.
-
B.
Napoleonic policy
Napoleonic policy refers to the strategic, administrative, legal, and military measures implemented by Napoleon Bonaparte to centralize authority, modernize state institutions, expand French influence, and consolidate his personal rule across Europe.
-
C.
oblast of the Russian Empire
An oblast of the Russian Empire was an administrative-territorial unit, typically on the empire’s periphery, governed by appointed officials and possessing a lower status than a governorate (guberniya).
-
D.
state institution of the Russian Empire
A state institution of the Russian Empire was an official governmental body or administrative organ responsible for implementing imperial policies, managing public affairs, and exercising authority within the empire’s centralized bureaucratic system.
-
E.
colonial policy
chosen
Colonial policy is the set of laws, strategies, and administrative practices through which a colonial power governs, exploits, and manages its colonies and their populations.
- 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_69bd463d956c819088105c3db802c017 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 1:59 p.m.