Triple
T15359990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunnmøre |
E367264
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Ulsteinvik |
E494768
|
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: Ulsteinvik | Statement: [Sunnmøre, hasTown, Ulsteinvik]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ulsteinvik Context triple: [Sunnmøre, hasTown, Ulsteinvik]
-
A.
Ulsteinvik
chosen
Ulsteinvik is a coastal town in western Norway known for its maritime industry and shipbuilding, serving as the administrative center of Ulstein Municipality.
-
B.
Bergvik
Bergvik is a small locality in central Sweden situated within Söderhamn Municipality in Gävleborg County.
-
C.
Håkvik
Håkvik is a small settlement in northern Norway, located within Narvik Municipality in Nordland county.
-
D.
Gressvik
Gressvik is a village in Fredrikstad Municipality in Viken county, Norway, located on the western side of the Glomma River.
-
E.
Svelvik
Svelvik is a small coastal town and former municipality in Vestfold og Telemark county, Norway, situated along the Drammensfjord.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e4607408190ab281a7f7a8012d3 |
completed | April 16, 2026, 1:41 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff5f2754648190bfd0bd15f20b40d2 |
completed | May 9, 2026, 4:21 p.m. |
Created at: April 10, 2026, 3:18 a.m.