Triple
T3241561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amager Island |
E67975
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Øresund |
E70875
|
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: Øresund | Statement: [Amager Island, locatedIn, Øresund]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Øresund Context triple: [Amager Island, locatedIn, Øresund]
-
A.
Øresund
chosen
Øresund is the strait between Denmark and Sweden that connects the Baltic Sea to the North Sea and is spanned by the Øresund Bridge.
-
B.
Kattegat
Kattegat is a shallow sea area and strait between Denmark and Sweden that forms a key maritime passage linking the North Sea with the Baltic Sea.
-
C.
Great Belt
The Great Belt is a major strait in Denmark that separates the islands of Funen and Zealand and connects the Baltic Sea to the Kattegat.
-
D.
Fehmarn Belt
Fehmarn Belt is a strait in the western Baltic Sea between the German island of Fehmarn and the Danish island of Lolland, serving as an important maritime passage and planned fixed-link corridor between Germany and Denmark.
-
E.
Skagerrak
Skagerrak is a strait and sea area between Norway, Denmark, and Sweden that connects the North Sea to the Baltic Sea.
- 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_69ad858d27348190abb61c280b4c86a9 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaef76d908190815bb456e366ee0a |
completed | March 8, 2026, 5:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b31a65d2988190a053eb2f22503f83 |
completed | March 12, 2026, 7:56 p.m. |
Created at: March 8, 2026, 3:08 p.m.