Triple
T20207422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riga–Jelgava railway |
E493388
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | Baltic railway network |
—
|
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: Baltic railway network | Statement: [Riga–Jelgava railway, partOf, Baltic railway network]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Baltic railway network Context triple: [Riga–Jelgava railway, partOf, Baltic railway network]
-
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.
Vilnius–Klaipėda Railway
The Vilnius–Klaipėda Railway is a major Lithuanian rail line connecting the capital city Vilnius with the Baltic Sea port city of Klaipėda, serving as a key passenger and freight corridor.
-
C.
Polish railway network
The Polish railway network is the nationwide system of rail lines and infrastructure in Poland that connects cities, towns, and regions for passenger and freight transport.
-
D.
Finnish railway network
The Finnish railway network is a nationwide system of rail lines connecting major cities, industrial centers, and remote regions across Finland, supporting both passenger and freight transport in a challenging Nordic climate.
-
E.
Vilnius–Daugavpils railway connection
The Vilnius–Daugavpils railway connection is an international rail line linking Lithuania’s capital Vilnius with the Latvian city of Daugavpils, serving as an important regional passenger and freight corridor between the two countries.
- 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: Baltic railway network Target entity description: The Baltic railway network is the interconnected system of rail lines across the Baltic states that links major cities, ports, and industrial centers to support regional and international transport.
-
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.
Vilnius–Klaipėda Railway
The Vilnius–Klaipėda Railway is a major Lithuanian rail line connecting the capital city Vilnius with the Baltic Sea port city of Klaipėda, serving as a key passenger and freight corridor.
-
C.
Polish railway network
The Polish railway network is the nationwide system of rail lines and infrastructure in Poland that connects cities, towns, and regions for passenger and freight transport.
-
D.
Finnish railway network
The Finnish railway network is a nationwide system of rail lines connecting major cities, industrial centers, and remote regions across Finland, supporting both passenger and freight transport in a challenging Nordic climate.
-
E.
Vilnius–Daugavpils railway connection
The Vilnius–Daugavpils railway connection is an international rail line linking Lithuania’s capital Vilnius with the Latvian city of Daugavpils, serving as an important regional passenger and freight corridor between the two countries.
- 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66d934f808190bbfeb96f5bf2dfb9 |
completed | April 20, 2026, 6:16 p.m. |
Created at: April 11, 2026, 11:38 p.m.