Triple
T31441464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russification of Finland |
E802075
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russification policy |
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: Russification policy Context triple: [Russification of Finland, instanceOf, Russification policy]
-
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.
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.
-
D.
Kulturkampf measure
A Kulturkampf measure is a governmental policy or legal action aimed at reducing the influence of religious institutions—especially the Catholic Church—over public life, education, and politics in favor of state control and secularization.
-
E.
Russian-style colony
A Russian-style colony is a settlement or territory established and controlled by Russia that reflects Russian governance, culture, language, and economic interests, often emphasizing centralized authority and strategic or resource-based exploitation.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:06 p.m.