Triple
T21934396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leontief paradox |
E541650
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | paradox in international trade theory |
C45549
|
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: paradox in international trade theory Context triple: [Leontief paradox, instanceOf, paradox in international trade theory]
-
A.
international trade dispute
An international trade dispute is a conflict between countries or trading entities over the interpretation, application, or alleged violation of trade agreements, policies, or practices affecting cross-border commerce.
-
B.
protectionist trade policy
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.
-
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.
trade policy regime
A trade policy regime is the structured set of laws, regulations, agreements, and institutional practices that govern a country’s international trade relations and market openness.
-
E.
trade policy expert
A trade policy expert is a specialist who analyzes, designs, and advises on international trade rules, agreements, and regulations to guide governments or organizations in achieving economic and strategic objectives.
- 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_69e0c47e2e5c81909a7f74ce3de50911 |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 7:51 p.m.