Triple
T1858593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arusha Declaration on Integrity in Customs |
E41761
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | customs integrity framework |
C2070
|
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 integrity framework Context triple: [Arusha Declaration on Integrity in Customs, instanceOf, customs integrity framework]
-
A.
intergovernmental working group framework
An intergovernmental working group framework is a structured, collaborative arrangement through which multiple governments coordinate, negotiate, and develop joint policies, standards, or actions on shared issues.
-
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.
border control program
A border control program is a coordinated set of policies, procedures, and technologies designed to regulate and monitor the movement of people and goods across a country's borders to ensure security, compliance, and lawful entry.
-
D.
international conservation framework
An international conservation framework is a coordinated set of globally agreed principles, policies, and mechanisms that guide countries and organizations in protecting biodiversity and natural resources across borders.
-
E.
international framework
chosen
An international framework is a structured set of principles, rules, and mechanisms agreed upon by multiple countries to guide cooperation, coordination, and decision-making on shared global issues.
- 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_69a8864a83848190a4ec02721306c511 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:33 p.m.