Triple
T23454382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sakshaug Church |
E567876
|
entity |
| Predicate | parish |
P2739
|
FINISHED |
| Object | Sakshaug parish |
—
|
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: Sakshaug parish | Statement: [Sakshaug Church, parish, Sakshaug parish]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sakshaug parish Context triple: [Sakshaug Church, parish, Sakshaug parish]
-
A.
Sakshaug parish
chosen
Sakshaug parish is a Church of Norway parish and historic ecclesiastical district located in the municipality of Inderøy in Trøndelag county, Norway.
-
B.
Alstahaug parish
Alstahaug parish is a Church of Norway parish serving the local community in the Alstahaug area of Nordland county.
-
C.
Haug parish
Haug parish is a local Church of Norway parish serving part of the Ringerike area in Buskerud, Norway.
-
D.
Volda parish
Volda parish is a Church of Norway parish serving the local Lutheran congregation in the municipality of Volda in western Norway.
-
E.
Rygge parish
Rygge parish is a Church of Norway parish serving the local community in the Rygge area of Østfold, Norway.
- 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_69e2458b4c888190b1d7998f9862a558 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a695fed08190bfa160e69200546d |
completed | April 29, 2026, 6:35 a.m. |
Created at: April 17, 2026, 5:53 p.m.