Triple
T15562922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leirvik |
E371041
|
entity |
| Predicate | hasNeighbouringSettlement |
P4647
|
FINISHED |
| Object | Sagvåg |
E1143789
|
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: Sagvåg | Statement: [Leirvik, hasNeighbouringSettlement, Sagvåg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sagvåg Context triple: [Leirvik, hasNeighbouringSettlement, Sagvåg]
-
A.
Sagvåg
chosen
Sagvåg is a village on the island municipality of Stord in Vestland county, Norway, known for its coastal setting and local maritime industry.
-
B.
Vikevåg
Vikevåg is a village in Rogaland county, Norway, known for its coastal setting and role in local administration and services.
-
C.
Brattvåg
Brattvåg is a small coastal village in western Norway known for its maritime industry and scenic fjord landscape.
-
D.
Kalvåg
Kalvåg is a coastal fishing village in Bremanger Municipality in Vestland county, Norway, known for its well-preserved wooden waterfront buildings and maritime heritage.
-
E.
Fosnavåg
Fosnavåg is a small coastal town in western Norway known for its maritime industries and scenic North Sea surroundings.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ddc66448190948280fb0c8d390c |
completed | April 16, 2026, 2:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a003c4303888190a93830ef534715ae |
completed | May 10, 2026, 8:05 a.m. |
Created at: April 10, 2026, 4:09 a.m.