Triple
T33342035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CEMAC Treaty |
E853696
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional economic integration treaty |
C27023
|
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: regional economic integration treaty Context triple: [CEMAC Treaty, instanceOf, regional economic integration treaty]
-
A.
regional economic integration protocol
chosen
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.
regional economic cooperation framework
A regional economic cooperation framework is an organized arrangement among neighboring countries to coordinate policies, reduce trade and investment barriers, and promote shared economic development and integration.
-
D.
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.
-
E.
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.
- 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:34 a.m.