Triple
T21719580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nordenskiöld Land |
E536118
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Bellsund |
—
|
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: Bellsund | Statement: [Nordenskiöld Land, borders, Bellsund]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bellsund Context triple: [Nordenskiöld Land, borders, Bellsund]
-
A.
Bellsund
chosen
Bellsund is a fjord on the west coast of Spitsbergen in the Svalbard archipelago, known for its Arctic landscapes, wildlife, and historical sites from early whaling and mining activities.
-
B.
Stokksund
Stokksund is a coastal village and former municipality in Trøndelag county, Norway, known for its fishing community and scenic maritime landscape.
-
C.
Sørvågen
Sørvågen is a small fishing village and tourist destination located on the island of Moskenesøya in Norway’s Lofoten archipelago.
-
D.
Eiksund Sound
Eiksund Sound is a coastal waterway in western Norway, known for its fjord-like landscape and the Eiksund Tunnel that runs beneath it.
-
E.
Bogesund
Bogesund is a locality in Sweden known for its surrounding archipelago landscape, forests, and recreational natural areas.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd96de818819084c268d4775a8e3a |
completed | April 27, 2026, 9:47 p.m. |
Created at: April 16, 2026, 6:47 p.m.