Triple
T34519845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nigeria Integrated Customs Information System |
E886249
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | customs information system |
C60808
|
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 information system Context triple: [Nigeria Integrated Customs Information System, instanceOf, customs information system]
-
A.
customs authority network
A customs authority network is an interconnected system of national and regional customs agencies that collaborate to monitor, regulate, and facilitate the cross-border movement of goods, information, and enforcement actions.
-
B.
customs intelligence agency
A customs intelligence agency is a specialized government body that collects, analyzes, and shares information to detect, prevent, and investigate customs-related offenses such as smuggling, fraud, and illicit trade.
-
C.
customs regulation
Customs regulation is the set of laws, policies, and procedures governing the control, taxation, and documentation of goods and people crossing international borders.
-
D.
customs office
A customs office is a government facility where officials inspect, regulate, and process goods and people crossing borders to enforce trade laws, collect duties, and ensure compliance with import and export regulations.
-
E.
World Customs Organization instrument
A World Customs Organization instrument is an official legal or technical tool—such as a convention, agreement, standard, or guideline—adopted by the WCO to harmonize and facilitate customs procedures and international trade.
- F. None of above. chosen
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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:01 a.m.