Triple
T7789136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Læsø |
E187329
|
entity |
| Predicate | hasPort |
P35
|
FINISHED |
| Object | Østerby Havn |
E695405
|
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: Østerby Havn | Statement: [Læsø, hasPort, Østerby Havn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Østerby Havn Context triple: [Læsø, hasPort, Østerby Havn]
-
A.
Østerby Havn
chosen
Østerby Havn is a small coastal village and harbor on the Danish island of Læsø, known for its fishing, marina facilities, and maritime character.
-
B.
Vesterø Havn
Vesterø Havn is a small coastal village and ferry port on the Danish island of Læsø in the Kattegat.
-
C.
Aarhus Bay
Aarhus Bay is a coastal body of water in eastern Jutland, Denmark, forming part of the Kattegat and serving as the maritime setting for the city of Aarhus.
-
D.
Køge Bay
Køge Bay is a shallow bay in the southwestern part of the Øresund Strait off eastern Zealand in Denmark, known for its coastal towns, beaches, and role as a recreational and maritime area near Copenhagen.
-
E.
Sundbyøster
Sundbyøster is a district of Copenhagen located on the island of Amager, known primarily as a residential urban 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_69ca82af2d2c8190963861f5e0b8bf21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cae7e8a0d08190b6d4ca560681eb35 |
completed | March 30, 2026, 9:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cbdea8e0ec8190a88dae9f0097ca16 |
completed | March 31, 2026, 2:48 p.m. |
Created at: March 30, 2026, 4:25 p.m.