Triple
T18833220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Djibouti–Addis Ababa road corridor |
E460587
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | trade corridor |
C1347
|
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: trade corridor Context triple: [Djibouti–Addis Ababa road corridor, instanceOf, trade corridor]
-
A.
transport corridor
A transport corridor is a designated route or geographic band that concentrates and connects major transportation infrastructure—such as roads, railways, ports, and logistics hubs—to facilitate efficient movement of people and goods between key locations.
-
B.
trade and transportation corridor initiative
A trade and transportation corridor initiative is a coordinated program to develop and optimize key routes, infrastructure, and policies that facilitate efficient movement of goods and people across regions or borders.
-
C.
road transportation corridor
chosen
A road transportation corridor is a designated linear area of land that accommodates one or more roadways and associated infrastructure to enable the efficient movement of vehicles, goods, and people between key origins and destinations.
-
D.
freight rail corridor
A freight rail corridor is a designated railway route primarily used for the efficient, high-capacity movement of goods and cargo between industrial, commercial, and logistics hubs.
-
E.
business corridor
A business corridor is a concentrated area along a major route or within a district where commercial, office, and retail activities are clustered to support economic activity and accessibility.
- 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:56 a.m.