Triple
T27562192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adriatic-Ionian transport corridor |
E695802
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | trans-European transport route |
C49884
|
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: trans-European transport route Context triple: [Adriatic-Ionian transport corridor, instanceOf, trans-European transport route]
-
A.
trans-European transport network route
chosen
A trans-European transport network route is a designated corridor within the EU-wide integrated transport system that connects key cities, ports, and regions across Europe to facilitate efficient, interoperable, and sustainable cross-border movement of people and goods.
-
B.
trans-European road
A trans-European road is a major transportation route that crosses multiple European countries, facilitating international travel and trade across the continent.
-
C.
Polish expressway
A Polish expressway is a high-capacity, limited-access road in Poland designed for fast regional and intercity traffic, typically featuring dual carriageways, grade-separated junctions, and controlled entry and exit points.
-
D.
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.
-
E.
road transportation corridor
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.
- 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 27, 2026, 1:39 p.m.