Triple
T16262962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trelleborg |
E394800
|
entity |
| Predicate | connectsByFerryTo |
P1831
|
FINISHED |
| Object | Sassnitz |
E123342
|
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: Sassnitz | Statement: [Trelleborg, connectsByFerryTo, Sassnitz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sassnitz Context triple: [Trelleborg, connectsByFerryTo, Sassnitz]
-
A.
Sassnitz
chosen
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.
-
B.
Ueckermünde
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.
-
C.
Stolpmünde
Stolpmünde is the former German name for the Baltic Sea port town now known as Ustka in northern Poland.
-
D.
Ostseebad
Ostseebad is a German designation for a seaside resort town on the Baltic Sea, recognized for its coastal tourism and spa facilities.
-
E.
Lüchow
Lüchow is a small historic town in Lower Saxony, Germany, known as an administrative and cultural center of the rural Wendland area.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c5583c8190901e892238cf8dbd |
completed | April 17, 2026, 2:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0017b5f3a8819083128cf2b90cfd84 |
completed | May 10, 2026, 5:29 a.m. |
Created at: April 10, 2026, 5:04 a.m.