Triple
T6809557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Szczecin Lagoon |
E156594
|
entity |
| Predicate | nearCity |
P350
|
FINISHED |
| Object | Ueckermünde |
E586148
|
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: Ueckermünde | Statement: [Szczecin Lagoon, nearCity, Ueckermünde]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ueckermünde Context triple: [Szczecin Lagoon, nearCity, Ueckermünde]
-
A.
Ueckermünde
chosen
Ueckermünde is a small historic port town in northeastern Germany on the Szczecin Lagoon, known for its maritime heritage and access to the Baltic Sea.
-
B.
Sassnitz
Sassnitz is a port town on the Baltic Sea coast of Germany, located on the island of Rügen and known as a gateway to nearby national parks and chalk cliffs.
-
C.
Heringsdorf
Heringsdorf is a seaside resort town on the Baltic Sea coast of the island of Usedom in northeastern Germany, known for its historic pier and spa architecture.
-
D.
Angermünde
Angermünde is a historic small town in northeastern Germany’s Brandenburg state, known for its medieval architecture and location within the rural Uckermark region.
-
E.
Prenzlau
Prenzlau is a historic town in northeastern Germany’s Brandenburg region, known for its medieval architecture and role as a regional administrative center.
- 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_69c68828b26c819090fe9df7612bbc27 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d30c741881909e220b05aa564bc2 |
completed | March 27, 2026, 6:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c71aa5411c81908d05bef3213b39f1 |
completed | March 28, 2026, 12:02 a.m. |
Created at: March 27, 2026, 2:16 p.m.