Triple
T15326674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet–Finnish trade agreements |
E366428
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bilateral trade agreement framework |
C19992
|
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: bilateral trade agreement framework Context triple: [Soviet–Finnish trade agreements, instanceOf, bilateral trade agreement framework]
-
A.
bilateral trade association
A bilateral trade association is an organization formed between two countries to promote, facilitate, and regulate trade and economic cooperation through agreements, advocacy, and joint initiatives.
-
B.
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.
-
C.
free trade area agreement
A free trade area agreement is a treaty between two or more countries that eliminates tariffs and other trade barriers on most goods and services traded among them while allowing each country to maintain its own external trade policies toward non-members.
-
D.
bilateral commission
A bilateral commission is a formal joint body established by two parties, typically states or organizations, to negotiate, coordinate, and oversee matters of mutual interest.
-
E.
trade policy mechanism
chosen
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.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:16 a.m.