Triple
T13357052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kvernes Stave Church |
E318719
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Bremnesfjord |
E316582
|
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: Bremnesfjord | Statement: [Kvernes Stave Church, locatedNear, Bremnesfjord]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bremnesfjord Context triple: [Kvernes Stave Church, locatedNear, Bremnesfjord]
-
A.
Bremnesfjorden
chosen
Bremnesfjorden is a fjord in Norway known for its coastal landscape along the island of Averøya.
-
B.
Namsenfjorden
Namsenfjorden is a fjord in Trøndelag county, Norway, known for its scenic coastal landscape and connection to the Namsen River near the town of Namsos.
-
C.
Beisfjorden
Beisfjorden is a fjord in Nordland county, Norway, known as an inner branch of the larger Ofotfjord near the town of Narvik.
-
D.
Orkdalsfjorden
Orkdalsfjorden is a branch of the Trondheimsfjord in central Norway, known for its narrow, fjord-like extension inland toward the town of Orkanger.
-
E.
Boknafjorden
Boknafjorden is a large fjord in Rogaland county in southwestern Norway, known for its many islands and role as an important maritime route.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69da62887e588190bd7241c720a112a2 |
completed | April 11, 2026, 3:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcdeea935081909baffaadc8a8fac7 |
completed | May 7, 2026, 6:50 p.m. |
Created at: April 9, 2026, 9:32 p.m.