Triple

T23358761
Position Surface form Disambiguated ID Type / Status
Subject Nynäshamn–Ventspils route E593124 entity
Predicate partOf P40 FINISHED
Object Sweden–Latvia transport links 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: Sweden–Latvia transport links | Statement: [Nynäshamn–Ventspils route, partOf, Sweden–Latvia transport links]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sweden–Latvia transport links
Context triple: [Nynäshamn–Ventspils route, partOf, Sweden–Latvia transport links]
  • A. Latvia eastbound transport corridor
    The Latvia eastbound transport corridor is a key transportation route facilitating rail and other eastward transit flows across Latvia toward neighboring regions and international markets.
  • B. Finland–Sweden traffic corridor
    The Finland–Sweden traffic corridor is a major cross-Baltic transport route linking Finland and Sweden via ferry and other connections, facilitating significant passenger and freight movement between the two countries.
  • 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. Tallinn–Helsinki
    Tallinn–Helsinki refers to the busy passenger and freight ferry connection across the Gulf of Finland linking the capitals of Estonia and Finland.
  • E. Tallinn–Stockholm
    Tallinn–Stockholm is a major international ferry route across the Baltic Sea connecting the capitals of Estonia and Sweden.
  • 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: Sweden–Latvia transport links
Target entity description: Sweden–Latvia transport links comprise the network of ferry routes, shipping lanes, and other transport connections facilitating passenger and cargo movement between Sweden and Latvia across the Baltic Sea.
  • A. Latvia eastbound transport corridor
    The Latvia eastbound transport corridor is a key transportation route facilitating rail and other eastward transit flows across Latvia toward neighboring regions and international markets.
  • B. Finland–Sweden traffic corridor
    The Finland–Sweden traffic corridor is a major cross-Baltic transport route linking Finland and Sweden via ferry and other connections, facilitating significant passenger and freight movement between the two countries.
  • 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. Tallinn–Helsinki
    Tallinn–Helsinki refers to the busy passenger and freight ferry connection across the Gulf of Finland linking the capitals of Estonia and Finland.
  • E. Tallinn–Stockholm
    Tallinn–Stockholm is a major international ferry route across the Baltic Sea connecting the capitals of Estonia and Sweden.
  • 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_69e25d24d2a4819092e6ede74c2a918d completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f19a196b308190bfe9bb4b6e7ec363 completed April 29, 2026, 5:41 a.m.
Created at: April 17, 2026, 5:29 p.m.