Triple
T13357034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kvernes Stave Church |
E318719
|
entity |
| Predicate | parish |
P2739
|
FINISHED |
| Object | Kvernes parish |
E1033405
|
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: Kvernes parish | Statement: [Kvernes Stave Church, parish, Kvernes parish]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kvernes parish Context triple: [Kvernes Stave Church, parish, Kvernes parish]
-
A.
Kvernes parish
chosen
Kvernes parish is a Church of Norway parish in western Norway that encompasses the historic Kvernes Church and serves the local Lutheran congregation in the surrounding area.
-
B.
Vestfossen parish
Vestfossen parish is a local Church of Norway parish centered on the village of Vestfossen in the municipality of Øvre Eiker in Buskerud, Norway.
-
C.
Rygge parish
Rygge parish is a Church of Norway parish serving the local community in the Rygge area of Østfold, Norway.
-
D.
Sandvollan parish
Sandvollan parish is a local Church of Norway parish serving the Sandvollan area within the municipality of Inderøy in Trøndelag county.
-
E.
Skiptvet parish
Skiptvet parish is a local Church of Norway parish serving the community of Skiptvet in Viken county, Norway.
- 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_69f72677b2a48190aad30f3ee6cacefb |
completed | May 3, 2026, 10:41 a.m. |
Created at: April 9, 2026, 9:32 p.m.