Triple
T12740066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mussolini’s autarky campaigns |
E304465
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | protectionist policy |
C2697
|
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: protectionist policy Context triple: [Mussolini’s autarky campaigns, instanceOf, protectionist policy]
-
A.
protectionist trade policy
chosen
Protectionist trade policy is a government strategy that restricts imports and/or promotes domestic industries through tools like tariffs, quotas, and subsidies to shield the national economy from foreign competition.
-
B.
trade policy instrument
A trade policy instrument is a specific tool or measure—such as tariffs, quotas, subsidies, or regulations—used by a government to influence international trade flows and economic outcomes.
-
C.
trade policy mechanism
A trade policy mechanism is a structured tool or set of rules—such as tariffs, quotas, subsidies, or trade agreements—used by governments to influence international trade flows, prices, and economic outcomes.
-
D.
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.
-
E.
preferential trade agreement
A preferential trade agreement is an arrangement between two or more countries to reduce tariffs and other trade barriers on certain products or services for member nations, granting them more favorable access than non-members.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:26 p.m.