Triple
T20396254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sigulda |
E500210
|
entity |
| Predicate | transportConnection |
P1298
|
FINISHED |
| Object | Riga–Valka railway line |
—
|
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: Riga–Valka railway line | Statement: [Sigulda, transportConnection, Riga–Valka railway line]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Riga–Valka railway line Context triple: [Sigulda, transportConnection, Riga–Valka railway line]
-
A.
Riga–Jelgava railway
The Riga–Jelgava railway is a key rail line in Latvia that links the capital city Riga with the nearby city of Jelgava, serving both passenger and freight traffic.
-
B.
Riga–Tukums railway
The Riga–Tukums railway is a key rail line in Latvia linking the capital Riga with the town of Tukums and serving as an important regional passenger and freight route.
-
C.
Riga–Daugavpils railway
The Riga–Daugavpils railway is a major rail line in Latvia that links the capital Riga with the country’s second-largest city, Daugavpils, serving as an important route for both passenger and freight transport.
-
D.
Riga–Aizkraukle railway
The Riga–Aizkraukle railway is a key Latvian rail line linking the capital Riga with the town of Aizkraukle and forming part of the country’s main eastbound transport corridor.
-
E.
Riga–Skulte railway
The Riga–Skulte railway is a Latvian rail line running from the capital city Riga northward toward the coastal town of Skulte, serving as an important regional passenger route.
- 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: Riga–Valka railway line Target entity description: The Riga–Valka railway line is a rail route in Latvia that connects the capital city Riga with the border town of Valka, passing through several regional centers including Sigulda.
-
A.
Riga–Jelgava railway
The Riga–Jelgava railway is a key rail line in Latvia that links the capital city Riga with the nearby city of Jelgava, serving both passenger and freight traffic.
-
B.
Riga–Tukums railway
The Riga–Tukums railway is a key rail line in Latvia linking the capital Riga with the town of Tukums and serving as an important regional passenger and freight route.
-
C.
Riga–Daugavpils railway
The Riga–Daugavpils railway is a major rail line in Latvia that links the capital Riga with the country’s second-largest city, Daugavpils, serving as an important route for both passenger and freight transport.
-
D.
Riga–Aizkraukle railway
The Riga–Aizkraukle railway is a key Latvian rail line linking the capital Riga with the town of Aizkraukle and forming part of the country’s main eastbound transport corridor.
-
E.
Riga–Skulte railway
The Riga–Skulte railway is a Latvian rail line running from the capital city Riga northward toward the coastal town of Skulte, serving as an important regional passenger route.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6798b6640819085d5b12dc35633fe |
completed | April 20, 2026, 7:07 p.m. |
Created at: April 16, 2026, 11:28 a.m.