Triple

T20099753
Position Surface form Disambiguated ID Type / Status
Subject Riga–Aizkraukle railway E496501 entity
Predicate partOf P40 FINISHED
Object Latvia eastbound 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: Latvia eastbound transport corridor | Statement: [Riga–Aizkraukle railway, partOf, Latvia eastbound transport corridor]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Latvia eastbound transport corridor
Context triple: [Riga–Aizkraukle railway, partOf, Latvia eastbound transport corridor]
  • 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. Rail Baltica corridor in Lithuania
    The Rail Baltica corridor in Lithuania is a key segment of the European-gauge high-speed rail project linking the Baltic States with the rest of the European rail network, running north–south through Lithuanian territory.
  • C. Latvian State Roads
    Latvian State Roads is the national government agency responsible for managing, maintaining, and developing the state road network in Latvia.
  • D. Riga–Moscow highway
    The Riga–Moscow highway is a major international road route connecting Latvia’s capital Riga with Russia’s capital Moscow, serving as an important corridor for regional transport and trade.
  • 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: Latvia eastbound transport corridor
Target entity description: 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.
  • 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. Rail Baltica corridor in Lithuania
    The Rail Baltica corridor in Lithuania is a key segment of the European-gauge high-speed rail project linking the Baltic States with the rest of the European rail network, running north–south through Lithuanian territory.
  • C. Latvian State Roads
    Latvian State Roads is the national government agency responsible for managing, maintaining, and developing the state road network in Latvia.
  • D. Riga–Moscow highway
    The Riga–Moscow highway is a major international road route connecting Latvia’s capital Riga with Russia’s capital Moscow, serving as an important corridor for regional transport and trade.
  • 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

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_69da626eee3881909f3454986d4a6511 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e6666f2298819089659f13556ca305 completed April 20, 2026, 5:46 p.m.
Created at: April 11, 2026, 11:26 p.m.