Triple
T14295504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | northwestern Poland |
E354427
|
entity |
| Predicate | containsPortCity |
P2745
|
FINISHED |
| Object | Świnoujście |
—
|
NE NERFINISHED |
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: Świnoujście | Statement: [northwestern Poland, containsPortCity, Świnoujście]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Świnoujście Context triple: [northwestern Poland, containsPortCity, Świnoujście]
-
A.
Świnoujście
chosen
Ś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.
-
B.
Świnica
Świnica is a prominent peak in the High Tatras on the Polish–Slovak border, popular with hikers for its rugged ridges and panoramic alpine views.
-
C.
Śniardwy
Śniardwy is the largest lake in Poland, located in the Masurian Lake District of northeastern Poland.
-
D.
Kwidzyn
Kwidzyn is a historic town in northern Poland known for its medieval Teutonic castle complex and Gothic cathedral.
-
E.
Olsztynek
Olsztynek is a small historic town in northern Poland known for its open-air ethnographic museum and location within the picturesque Warmian-Masurian lake district.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de717b35ec81908968994e65737c66 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:11 a.m.