Triple
T33396652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty on the Eurasian Economic Union |
E855190
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | economic integration treaty |
C566
|
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 integration treaty Context triple: [Treaty on the Eurasian Economic Union, instanceOf, economic integration treaty]
-
A.
regional economic integration protocol
A regional economic integration protocol is a formal agreement among neighboring or closely linked countries that coordinates trade, investment, and regulatory policies to reduce barriers and promote a more unified regional market.
-
B.
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.
-
C.
bilateral economic agreement
A bilateral economic agreement is a formal arrangement between two countries that establishes rules and commitments to govern their economic relations, such as trade, investment, and financial cooperation.
-
D.
European Union treaty protocol
A European Union treaty protocol is a formal, legally binding addendum or supplement to an EU founding or amending treaty that clarifies, extends, or specifies particular provisions, obligations, or arrangements among member states.
-
E.
treaty
chosen
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
- 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:35 a.m.