Triple
T6426035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trondheimsfjord |
E128059
|
entity |
| Predicate | nearIsland |
P19486
|
FINISHED |
| Object | Munkholmen |
E570932
|
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: Munkholmen | Statement: [Trondheimsfjord, nearIsland, Munkholmen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Munkholmen Context triple: [Trondheimsfjord, nearIsland, Munkholmen]
-
A.
Munkholmen
chosen
Munkholmen is a small historic island off Trondheim, Norway, known for its past roles as a monastery, fortress, prison, and World War II defensive site, and today as a popular tourist destination.
-
B.
Kastellholmen
Kastellholmen is a small island in central Stockholm, Sweden, known for its historic red-brick citadel and scenic waterfront views.
-
C.
Skärholmen
Skärholmen is a suburban district in southwestern Stockholm, Sweden, known for its large shopping center and residential areas.
-
D.
Storholmen
Storholmen is an island located in Lake Femunden, one of Norway’s largest inland lakes.
-
E.
Stadsholmen
Stadsholmen is the central island in Stockholm’s historic Gamla stan (Old Town), known for its medieval street layout and well-preserved architecture.
- 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_69c00838de888190af2eec0b80495efa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0691f944c81909d4e5d8ef9e494b6 |
completed | March 22, 2026, 10:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c640e339108190bbb74c688de574cc |
completed | March 27, 2026, 8:33 a.m. |
Created at: March 22, 2026, 4:43 p.m.