Triple
T32479271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peruvian border control at Santa Rosa |
E830063
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | customs control facility |
C57313
|
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 control facility Context triple: [Peruvian border control at Santa Rosa, instanceOf, customs control facility]
-
A.
customs office
chosen
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.
-
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.
United States customs office
A United States customs office is a government facility where officials inspect, regulate, and process goods and people entering or leaving the country to enforce trade laws, collect duties, and ensure compliance with customs regulations.
-
D.
customs audit authority
A customs audit authority is an official body responsible for reviewing and verifying the accuracy, legality, and compliance of customs declarations, duties, and related trade activities.
-
E.
customs official
A customs official is a government agent responsible for enforcing laws and regulations on goods and people crossing borders, including inspections, documentation checks, and duty collection.
- 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_69f3491ff3b48190b50a7fa00bb05b1f |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:58 a.m.