Triple
T13084677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rålambshovsparken |
E310299
|
entity |
| Predicate | hasView |
P854
|
FINISHED |
| Object | Riddarfjärden |
E508255
|
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: Riddarfjärden | Statement: [Rålambshovsparken, hasView, Riddarfjärden]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Riddarfjärden Context triple: [Rålambshovsparken, hasView, Riddarfjärden]
-
A.
Riddarfjärden
chosen
Riddarfjärden is the easternmost bay of Lake Mälaren in central Stockholm, known for its iconic city skyline views and historic waterfront.
-
B.
Askrikefjärden
Askrikefjärden is a bay in the inner Stockholm archipelago in Sweden, known for its coastal landscapes and recreational boating waters.
-
C.
Kalmarsund
Kalmarsund is a strait in the Baltic Sea that separates the Swedish island of Öland from the mainland province of Småland.
-
D.
Brunnsviken
Brunnsviken is a scenic bay in the Stockholm area of Sweden, known for its surrounding parks, recreational areas, and cultural landmarks.
-
E.
Mossesundet
Mossesundet is a strait in southeastern Norway that separates the town of Moss from the island of Jeløya.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d981361e8c819099376435aa3a7aa3 |
completed | April 10, 2026, 11:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6f5cafd6c81908cb16bc0129ae74e |
completed | May 3, 2026, 7:14 a.m. |
Created at: April 9, 2026, 9:02 p.m.