Triple
T5987967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rügen Bridge |
E133274
|
entity |
| Predicate | locatedInBodyOfWater |
P1714
|
FINISHED |
| Object | Strelasund |
E515910
|
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: Strelasund | Statement: [Rügen Bridge, locatedInBodyOfWater, Strelasund]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Strelasund Context triple: [Rügen Bridge, locatedInBodyOfWater, Strelasund]
-
A.
Strelasund
chosen
Strelasund is a strait in the Baltic Sea separating the German island of Rügen from the mainland near the city of Stralsund.
-
B.
Kalmarsund
Kalmarsund is a strait in the Baltic Sea that separates the Swedish island of Öland from the mainland province of Småland.
-
C.
Norrsundet
Norrsundet is a small coastal locality in eastern Sweden known historically for its sawmill and harbor along the Gulf of Bothnia.
-
D.
Karmsundet
Karmsundet is a narrow strait in Rogaland county, Norway, separating the island of Karmøy from the mainland and forming part of the historic sailing route along the Norwegian coast.
-
E.
Skurusundet
Skurusundet is a narrow strait in the Stockholm archipelago of Sweden, known for its scenic waterfront, bridges, and residential surroundings.
- 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_69c0087010d081908bb8142342d63330 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04dc51d948190bacf4c40a73e91b2 |
completed | March 22, 2026, 8:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c2439f6cc08190bb7a4c6a0b7727c6 |
completed | March 24, 2026, 7:56 a.m. |
Created at: March 22, 2026, 4:04 p.m.