Triple
T35465836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chile–Bolivia transport network |
E1025070
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | binational transport network |
C9303
|
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: binational transport network Context triple: [Chile–Bolivia transport network, instanceOf, binational transport network]
-
A.
transport infrastructure network
A transport infrastructure network is an interconnected system of physical routes and facilities—such as roads, railways, ports, and airports—designed to enable the efficient movement of people and goods across regions.
-
B.
cross-border transport link
chosen
A cross-border transport link is an infrastructure connection—such as a road, railway, bridge, tunnel, or ferry route—that enables the movement of people and goods between two or more countries.
-
C.
border crossings network
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.
-
D.
road–rail border crossing
A road–rail border crossing is a designated point at an international boundary where both road and railway transport routes intersect or pass through, enabling the controlled movement of vehicles, trains, goods, and passengers between neighboring countries.
-
E.
public transport bridge
A public transport bridge is a dedicated crossing structure designed primarily for buses, trams, trains, or other mass transit vehicles to traverse obstacles such as rivers, roads, or valleys efficiently and safely.
- 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_69f76dfa20d0819089585dc2cf653aea |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.