Triple
T8850020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Convention on the Simplification and Harmonization of Customs Procedures |
E210614
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | customs 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: customs treaty Context triple: [International Convention on the Simplification and Harmonization of Customs Procedures, instanceOf, customs treaty]
-
A.
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.
-
B.
customs duty
Customs duty is a tax imposed by a government on goods imported into (and sometimes exported from) a country, typically calculated based on the value, quantity, or type of goods.
-
C.
treaty port concession
A treaty port concession is a designated area within a host country’s port where, under unequal treaty arrangements, foreign powers exercise special commercial, legal, and administrative privileges distinct from local jurisdiction.
-
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.
border treaty
A border treaty is a formal agreement between two or more states that defines, clarifies, or adjusts their mutual territorial boundaries and the rules governing them.
- 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_69ca838a424c8190b1ecac115c2927e7 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:49 p.m.