Triple
T15655643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kopervik |
E376430
|
entity |
| Predicate | locatedNorthOf |
P305
|
FINISHED |
| Object | Skudeneshavn |
E414652
|
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: Skudeneshavn | Statement: [Kopervik, locatedNorthOf, Skudeneshavn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Skudeneshavn Context triple: [Kopervik, locatedNorthOf, Skudeneshavn]
-
A.
Skudeneshavn
chosen
Skudeneshavn is a historic coastal town in southwestern Norway known for its well-preserved wooden architecture and maritime heritage.
-
B.
Farsund
Farsund is a coastal town and municipality in southern Norway known for its maritime heritage, beaches, and historic wooden architecture.
-
C.
Bremsnes
Bremsnes is a village on the island of Averøya in Møre og Romsdal county, Norway, known for its coastal setting and local church.
-
D.
Grimstad
Grimstad is a coastal town and municipality in southern Norway known for its maritime heritage, charming wooden houses, and role as a summer tourist destination.
-
E.
Haugesund
Haugesund is a coastal city in southwestern Norway known for its maritime heritage, shipbuilding industry, and annual film and jazz festivals.
- 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ef1f83c8190bbf65eed162cbd55 |
completed | April 16, 2026, 2:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a012ec19c508190912c3fe186f8a992 |
completed | May 11, 2026, 1:20 a.m. |
Created at: April 10, 2026, 4:15 a.m.