Triple
T14645259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sundbyøster |
E343828
|
entity |
| Predicate | sharesIslandWith |
P5790
|
FINISHED |
| Object | Sundbyvester |
E342321
|
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: Sundbyvester | Statement: [Sundbyøster, sharesIslandWith, Sundbyvester]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sundbyvester Context triple: [Sundbyøster, sharesIslandWith, Sundbyvester]
-
A.
Sundbyvester
chosen
Sundbyvester is a district of Copenhagen located on Amager Island, known primarily as a residential urban area.
-
B.
Sundby
Sundby is a district on the island of Amager in Copenhagen, Denmark, encompassing the neighborhoods of Sundbyvester and Sundbyøster.
-
C.
Sundbyøster
Sundbyøster is a district of Copenhagen located on the island of Amager, known primarily as a residential urban area.
-
D.
Rødby
Rødby is a small town on the Danish island of Lolland, known historically as a ferry port linking Denmark and Germany across the Baltic Sea.
-
E.
Nørresundby
Nørresundby is a town in northern Denmark situated across the Limfjord from Aalborg, forming part of the Aalborg metropolitan 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4ea6d8481908e6331ca173c646b |
completed | April 14, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdfb7ab30c8190af49268b6f93aeb1 |
completed | May 8, 2026, 3:04 p.m. |
Created at: April 10, 2026, 1:26 a.m.