Triple
T19961065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IC |
E479813
|
entity |
| Predicate | typicalRoutesInclude |
P13416
|
FINISHED |
| Object | Warsaw–Poznań 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: Warsaw–Poznań corridor | Statement: [IC, typicalRoutesInclude, Warsaw–Poznań corridor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Warsaw–Poznań corridor Context triple: [IC, typicalRoutesInclude, Warsaw–Poznań corridor]
-
A.
Warsaw–Wrocław corridor
The Warsaw–Wrocław corridor is a major intercity rail route in Poland linking the capital Warsaw with the southwestern city of Wrocław.
-
B.
Warsaw–Gdańsk corridor
The Warsaw–Gdańsk corridor is a major rail and transport route in Poland linking the capital city Warsaw with the Baltic port city of Gdańsk.
-
C.
Warsaw–Kraków corridor
The Warsaw–Kraków corridor is a major Polish rail and transport axis linking the capital Warsaw with the historic city of Kraków, serving as one of the country’s busiest passenger routes.
-
D.
Prague–Nuremberg corridor
The Prague–Nuremberg corridor is a major trans-European transport route linking the Czech capital Prague with the German city of Nuremberg, facilitating significant regional and international traffic and trade.
-
E.
Polish Corridor
The Polish Corridor was a strip of territory that gave the Second Polish Republic access to the Baltic Sea after World War I, separating East Prussia from the rest of Germany and becoming a major source of German-Polish tension before World War II.
- 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: Warsaw–Poznań corridor Target entity description: The Warsaw–Poznań corridor is a major rail and transport route in central Poland linking the capital Warsaw with the western city of Poznań, serving as a key axis for passenger and freight traffic.
-
A.
Warsaw–Wrocław corridor
The Warsaw–Wrocław corridor is a major intercity rail route in Poland linking the capital Warsaw with the southwestern city of Wrocław.
-
B.
Warsaw–Gdańsk corridor
The Warsaw–Gdańsk corridor is a major rail and transport route in Poland linking the capital city Warsaw with the Baltic port city of Gdańsk.
-
C.
Warsaw–Kraków corridor
The Warsaw–Kraków corridor is a major Polish rail and transport axis linking the capital Warsaw with the historic city of Kraków, serving as one of the country’s busiest passenger routes.
-
D.
Prague–Nuremberg corridor
The Prague–Nuremberg corridor is a major trans-European transport route linking the Czech capital Prague with the German city of Nuremberg, facilitating significant regional and international traffic and trade.
-
E.
Polish Corridor
The Polish Corridor was a strip of territory that gave the Second Polish Republic access to the Baltic Sea after World War I, separating East Prussia from the rest of Germany and becoming a major source of German-Polish tension before World War II.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65af4520c81909986a47289ba801e |
completed | April 20, 2026, 4:57 p.m. |
Created at: April 10, 2026, 1:54 p.m.