Triple
T20367271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Åfjord |
E496945
|
entity |
| Predicate | hasChurch |
P15000
|
FINISHED |
| Object | Åfjord Church |
—
|
NE NERFINISHED |
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: Åfjord Church | Statement: [Åfjord, hasChurch, Åfjord Church]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Åfjord Church Context triple: [Åfjord, hasChurch, Åfjord Church]
-
A.
Åfjord Church
chosen
Åfjord Church is a parish church of the Church of Norway located in the coastal municipality of Åfjord in Trøndelag county.
-
B.
Austefjord Church
Austefjord Church is a parish church of the Church of Norway located in the village of Austefjord in Volda Municipality, Møre og Romsdal county.
-
C.
Eresfjord Church
Eresfjord Church is a parish church in Norway serving the local community of Eresfjord with traditional Lutheran worship and regional cultural significance.
-
D.
Billefjord Church
Billefjord Church is a small parish church serving the local community in the village of Billefjord in Porsanger, Norway.
-
E.
Tysfjord Church
Tysfjord Church is a parish church in Nordland county, Norway, serving the local community of Tysfjord with traditional Lutheran worship.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4a4f9b081908a5a021919c21ccb |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6787291d88190a526fe2461d2a7c6 |
completed | April 20, 2026, 7:03 p.m. |
Created at: April 16, 2026, 11:26 a.m.