Triple
T6251770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fetlar Kirk |
E140060
|
entity |
| Predicate | parish |
P2739
|
FINISHED |
| Object | Fetlar parish |
E26067
|
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: Fetlar parish | Statement: [Fetlar Kirk, parish, Fetlar parish]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fetlar parish Context triple: [Fetlar Kirk, parish, Fetlar parish]
-
A.
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.
-
B.
Østerlars Parish
Østerlars Parish is an ecclesiastical and administrative parish on the Danish island of Bornholm, centered around the historic round church of Østerlars.
-
C.
Fetlar
chosen
Fetlar is one of the Shetland Islands in Scotland, known for its rich birdlife and rural landscapes.
-
D.
Haug parish
Haug parish is a local Church of Norway parish serving part of the Ringerike area in Buskerud, Norway.
-
E.
Sakshaug parish
Sakshaug parish is a Church of Norway parish and historic ecclesiastical district located in the municipality of Inderøy in Trøndelag 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_69c008b4858c819095b0199114a9a87b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0633fb2ac8190b71b8e35fa923300 |
completed | March 22, 2026, 9:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c244240b448190be3645177194ced6 |
completed | March 24, 2026, 7:58 a.m. |
Created at: March 22, 2026, 4:24 p.m.