Triple
T17371206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Via Baltica (European route E67) |
E422317
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | Via Baltica |
—
|
NE ONNED1 |
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: Via Baltica | Statement: [Via Baltica (European route E67), name, Via Baltica]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Via Baltica Context triple: [Via Baltica (European route E67), name, Via Baltica]
-
A.
Baltic coast transport corridor
The Baltic coast transport corridor is a major transnational route along the southern Baltic Sea that facilitates regional and international trade and travel between coastal cities and ports.
-
B.
Baltic-Adriatic Corridor
The Baltic-Adriatic Corridor is a major trans-European transport route linking ports on the Baltic Sea with those on the Adriatic, facilitating north–south trade and mobility across Central Europe.
-
C.
Scandinavia–Russia transport corridor
The Scandinavia–Russia transport corridor is a major international route facilitating road and trade connections between the Nordic countries and the Russian Federation.
-
D.
North Sea–Mediterranean transport corridor
The North Sea–Mediterranean transport corridor is a major trans-European transport route that links key North Sea ports with the Mediterranean region via multimodal connections, including extensive inland waterways, rail, and road networks.
-
E.
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.
- 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: Via Baltica Target entity description: Via Baltica is a major north–south European highway corridor (European route E67) connecting Central Europe with the Baltic states and Finland.
-
A.
Baltic coast transport corridor
The Baltic coast transport corridor is a major transnational route along the southern Baltic Sea that facilitates regional and international trade and travel between coastal cities and ports.
-
B.
Baltic-Adriatic Corridor
The Baltic-Adriatic Corridor is a major trans-European transport route linking ports on the Baltic Sea with those on the Adriatic, facilitating north–south trade and mobility across Central Europe.
-
C.
Scandinavia–Russia transport corridor
The Scandinavia–Russia transport corridor is a major international route facilitating road and trade connections between the Nordic countries and the Russian Federation.
-
D.
North Sea–Mediterranean transport corridor
The North Sea–Mediterranean transport corridor is a major trans-European transport route that links key North Sea ports with the Mediterranean region via multimodal connections, including extensive inland waterways, rail, and road networks.
-
E.
Scandinavia–Central Europe transport corridor
chosen
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.
- F. None of above.
Provenance (3 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a68ff448190b505861e56df5b6d |
completed | April 19, 2026, 2:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a019568a27c8190af1bbe6db75f3e6f |
in_progress | May 11, 2026, 8:38 a.m. |
Created at: April 10, 2026, 5:44 a.m.