Triple
T19816842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skeppsholmen |
E476079
|
entity |
| Predicate | connectedByBridgeTo |
P845
|
FINISHED |
| Object | Blasieholmen |
—
|
NE NERFINISHED |
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: Blasieholmen | Statement: [Skeppsholmen, connectedByBridgeTo, Blasieholmen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Blasieholmen Context triple: [Skeppsholmen, connectedByBridgeTo, Blasieholmen]
-
A.
Blasieholmen
chosen
Blasieholmen is a central Stockholm peninsula known for its historic buildings, cultural institutions, and waterfront views across from the Old Town.
-
B.
Helgeandsholmen
Helgeandsholmen is a small central Stockholm islet best known as the site of the Swedish Parliament building and part of the historic city core.
-
C.
Kastellholmen
Kastellholmen is a small island in central Stockholm, Sweden, known for its historic red-brick citadel and scenic waterfront views.
-
D.
Liljeholmen
Liljeholmen is a district in southern Stockholm, Sweden, known for its waterfront location, residential areas, and commercial centers.
-
E.
Røsholmholmen
Røsholmholmen is a small island located in Tyrifjorden, a large lake in southeastern Norway.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e654f9c5b08190987237f5144c3b37 |
completed | April 20, 2026, 4:31 p.m. |
Created at: April 10, 2026, 1:50 p.m.