Triple
T18908395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pardubice hlavní nádraží |
E462528
|
entity |
| Predicate | railwayLine |
P848
|
FINISHED |
| Object | Prague–Česká Třebová 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: Prague–Česká Třebová railway line | Statement: [Pardubice hlavní nádraží, railwayLine, Prague–Česká Třebová railway line]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Prague–Česká Třebová railway line Context triple: [Pardubice hlavní nádraží, railwayLine, Prague–Česká Třebová railway line]
-
A.
Prague–Plzeň railway line
The Prague–Plzeň railway line is a major Czech rail corridor connecting the capital city Prague with the industrial and regional hub of Plzeň, serving both passenger and freight traffic.
-
B.
Prague–Hradec Králové railway
The Prague–Hradec Králové railway is a major Czech rail route connecting the capital city of Prague with the regional center of Hradec Králové, serving both passenger and freight traffic in Bohemia.
-
C.
Prague–Brno railway
The Prague–Brno railway is a major Czech rail corridor connecting the capital city Prague with the country’s second-largest city Brno, serving as a key route for both passenger and freight transport.
-
D.
Plzeň–Cheb railway line
The Plzeň–Cheb railway line is a major rail route in western Czechia connecting the city of Plzeň with the border city of Cheb and forming part of an important corridor toward Germany.
-
E.
Ostrava–Praha line
The Ostrava–Praha line is a major Czech railway corridor connecting the industrial city of Ostrava with the capital Prague, serving as one of the country’s busiest passenger and freight routes.
- 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: Prague–Česká Třebová railway line Target entity description: The Prague–Česká Třebová railway line is a major Czech rail corridor connecting Prague with eastern Bohemia and Moravia, forming part of an important national and international transit route.
-
A.
Prague–Plzeň railway line
The Prague–Plzeň railway line is a major Czech rail corridor connecting the capital city Prague with the industrial and regional hub of Plzeň, serving both passenger and freight traffic.
-
B.
Prague–Hradec Králové railway
The Prague–Hradec Králové railway is a major Czech rail route connecting the capital city of Prague with the regional center of Hradec Králové, serving both passenger and freight traffic in Bohemia.
-
C.
Prague–Brno railway
The Prague–Brno railway is a major Czech rail corridor connecting the capital city Prague with the country’s second-largest city Brno, serving as a key route for both passenger and freight transport.
-
D.
Plzeň–Cheb railway line
The Plzeň–Cheb railway line is a major rail route in western Czechia connecting the city of Plzeň with the border city of Cheb and forming part of an important corridor toward Germany.
-
E.
Ostrava–Praha line
The Ostrava–Praha line is a major Czech railway corridor connecting the industrial city of Ostrava with the capital Prague, serving as one of the country’s busiest passenger and freight routes.
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c52eed1881908929dace845ae008 |
completed | April 20, 2026, 6:18 a.m. |
Created at: April 10, 2026, 11:58 a.m.