Triple
T9834724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosenbad |
E239070
|
entity |
| Predicate | locatedOpposite |
P3232
|
FINISHED |
| Object | Helgeandsholmen |
E297374
|
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: Helgeandsholmen | Statement: [Rosenbad, locatedOpposite, Helgeandsholmen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Helgeandsholmen Context triple: [Rosenbad, locatedOpposite, Helgeandsholmen]
-
A.
Helgeandsholmen
chosen
Helgeandsholmen is a small central Stockholm islet best known as the site of the Swedish Parliament building and part of the historic city core.
-
B.
Røsholmholmen
Røsholmholmen is a small island located in Tyrifjorden, a large lake in southeastern Norway.
-
C.
Heggholmen
Heggholmen is a small island in the Oslofjord near Oslo, Norway, known for its coastal scenery and proximity to other islets like Gressholmen.
-
D.
Stadsholmen
Stadsholmen is the central island in Stockholm’s historic Gamla stan (Old Town), known for its medieval street layout and well-preserved architecture.
-
E.
Gressholmen
Gressholmen is a small recreational island near central Oslo, Norway, known for its beaches, nature reserve areas, and former seaplane airport.
- 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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3385054819094145c96204e3f0d |
completed | April 2, 2026, 12:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1d5c8f1a48190a4e7b6cda8ee88d5 |
completed | April 5, 2026, 3:23 a.m. |
Created at: March 30, 2026, 8:32 p.m.