Triple
T1187279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Defence and Economic Co-operation Treaty of 1950 |
E25275
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | economic cooperation agreement |
C824
|
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: economic cooperation agreement Context triple: [Joint Defence and Economic Co-operation Treaty of 1950, instanceOf, economic cooperation agreement]
-
A.
Economic alliance
An economic alliance is a formal or informal partnership between countries or regions designed to promote mutual economic benefits through cooperation in trade, investment, and financial policies.
-
B.
international agreement
chosen
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
-
C.
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.
-
D.
international economic organization
An international economic organization is an institution formed by multiple countries to coordinate and regulate economic policies, trade, finance, and development across national borders.
-
E.
economic ministry
An economic ministry is a government department responsible for formulating and implementing national economic policy, including fiscal strategy, economic planning, and oversight of key economic sectors.
- 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
Created at: March 1, 2026, 7:45 p.m.