Triple
T21395284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D3 motorway |
E527762
|
entity |
| Predicate | partOfCorridor |
P840
|
FINISHED |
| Object | Prague–Linz transport corridor |
—
|
NE NERFINISHED |
How this triple was built (3 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Prague–Linz transport corridor | Statement: [D3 motorway, partOfCorridor, Prague–Linz transport corridor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Prague–Linz transport corridor Context triple: [D3 motorway, partOfCorridor, Prague–Linz transport corridor]
-
A.
Berlin–Prague–Vienna transport corridor
The Berlin–Prague–Vienna transport corridor is a major trans-European route linking the German, Czech, and Austrian capitals by an integrated network of rail and road infrastructure.
-
B.
Brno–Vienna corridor
The Brno–Vienna corridor is a major Central European transport and development axis linking the Czech city of Brno with Austria’s capital Vienna, supporting regional connectivity and economic integration.
-
C.
Hungary–Austria road corridor
The Hungary–Austria road corridor is a major cross-border transport route linking Hungary and Austria and facilitating regional travel and trade between the two countries.
-
D.
Scandinavia–Central Europe transport corridor
The Scandinavia–Central Europe transport corridor is a key trans-European route that links the Nordic countries with central European regions through a network of road, rail, and maritime connections.
-
E.
Ljubljana–Maribor corridor
The Ljubljana–Maribor corridor is a key Slovenian transport route linking the capital Ljubljana with the country’s second-largest city, Maribor, and forming part of an important pan-European transit axis.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Prague–Linz transport corridor Target entity description: The Prague–Linz transport corridor is a major planned Central European route intended to link the Czech capital Prague with the Austrian city of Linz via a modern motorway and rail connection.
-
A.
Berlin–Prague–Vienna transport corridor
The Berlin–Prague–Vienna transport corridor is a major trans-European route linking the German, Czech, and Austrian capitals by an integrated network of rail and road infrastructure.
-
B.
Brno–Vienna corridor
The Brno–Vienna corridor is a major Central European transport and development axis linking the Czech city of Brno with Austria’s capital Vienna, supporting regional connectivity and economic integration.
-
C.
Hungary–Austria road corridor
The Hungary–Austria road corridor is a major cross-border transport route linking Hungary and Austria and facilitating regional travel and trade between the two countries.
-
D.
Scandinavia–Central Europe transport corridor
The Scandinavia–Central Europe transport corridor is a key trans-European route that links the Nordic countries with central European regions through a network of road, rail, and maritime connections.
-
E.
Ljubljana–Maribor corridor
The Ljubljana–Maribor corridor is a key Slovenian transport route linking the capital Ljubljana with the country’s second-largest city, Maribor, and forming part of an important pan-European transit axis.
- F. None of above. chosen
Provenance (2 batches)
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_69e0b51ff3748190935c0a513c62a12b |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69ee62cd30f08190aba90afed6116a2a |
completed | April 26, 2026, 7:09 p.m. |
Created at: April 16, 2026, 5:13 p.m.