Triple
T10124202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Customs Union Protocol of the East African Community |
E223371
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | customs union protocol |
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: customs union protocol Context triple: [Customs Union Protocol of the East African Community, instanceOf, customs union protocol]
-
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.
World Customs Organization convention
A World Customs Organization convention is an international agreement established under the auspices of the WCO that harmonizes and standardizes customs procedures, rules, and practices among member countries to facilitate trade and ensure compliance.
-
C.
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.
-
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.
currency union
A currency union is an agreement between two or more countries to share a common currency and monetary policy, typically managed by a joint central authority.
- 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_69ca8422047c81909d66b717b8b18cf3 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 9:05 p.m.