Triple
T4892136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PKP Intercity |
E109587
|
entity |
| Predicate | servesStation |
P839
|
FINISHED |
| Object | Szczecin Główny |
E27720
|
NE FINISHED |
How this triple was built (2 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: Szczecin Główny | Statement: [PKP Intercity, servesStation, Szczecin Główny]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Szczecin Główny Context triple: [PKP Intercity, servesStation, Szczecin Główny]
-
A.
Szczecin
chosen
Szczecin is a large Polish city and important maritime and industrial center in northwestern Poland, situated near the Baltic Sea and the German border.
-
B.
Świnoujście
Świnoujście is a Polish port city and seaside resort on the Baltic Sea, known for its wide beaches, spa facilities, and strategic location at the mouth of the Świna River.
-
C.
Bydgoszcz
Bydgoszcz is a major city in northern Poland known as an important economic, cultural, and academic center on the Brda and Vistula rivers.
-
D.
Koszalin
Koszalin is a city in northwestern Poland near the Baltic Sea, known as a regional cultural and economic center.
-
E.
Gdańsk
Gdańsk is a major Polish port city on the Baltic Sea, known for its rich Hanseatic history, shipyards, and role in the origins of the Solidarity movement.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69bd4410bbf88190aad50d2451c863d6 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e2444dc819088d5562e90d16d9b |
completed | March 20, 2026, 3:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69beef8be078819094cbf65b0fcdf8dd |
completed | March 21, 2026, 7:20 p.m. |
Created at: March 20, 2026, 1:28 p.m.