Triple
T1144445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reduction of the Swedish nobility’s estates |
E23531
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | confiscation policy |
C6356
|
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: confiscation policy Context triple: [Reduction of the Swedish nobility’s estates, instanceOf, confiscation policy]
-
A.
colonial policy
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.
-
B.
economic blockade policy
An economic blockade policy is a state-led strategy that restricts or cuts off trade, financial transactions, and other economic interactions with a target nation or entity to exert political pressure or compel behavioral change.
-
C.
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.
-
D.
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.
-
E.
trade embargo
A trade embargo is a government-imposed restriction that partially or completely prohibits commercial exchange of goods and services with a specific country, group, or entity for political, economic, or security reasons.
- F. None of above. chosen
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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:44 p.m.