Triple
T38480763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexico–United States border crossings |
E915667
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | port of entry network |
C33262
|
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: port of entry network Context triple: [Mexico–United States border crossings, instanceOf, port of entry network]
-
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.
border crossings network
chosen
A border crossings network is a connected system of official entry and exit points, routes, and control infrastructures that manage and facilitate the movement of people, goods, and vehicles between neighboring jurisdictions.
-
C.
port authority
A port authority is an organization responsible for managing, regulating, and developing a seaport or group of ports, including their infrastructure, operations, and related maritime activities.
-
D.
border post
A border post is an official checkpoint facility located at or near a national boundary where authorities control and monitor the movement of people, goods, and vehicles between countries.
-
E.
group of international border crossings
A group of international border crossings is a collection of geographically or administratively related points where people, goods, and vehicles are legally permitted to pass between two or more countries.
- 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:31 p.m.