Triple
T19579905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skien Church |
E489958
|
entity |
| Predicate | parish |
P2739
|
FINISHED |
| Object | Skien 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: Skien parish | Statement: [Skien Church, parish, Skien parish]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Skien parish Context triple: [Skien Church, parish, Skien parish]
-
A.
Skien parish
chosen
Skien parish is a Church of Norway parish serving the town and surrounding area of Skien in Telemark, Norway.
-
B.
Skien Municipality
Skien Municipality is a local government area in Vestfold og Telemark county, Norway, encompassing the city of Skien and its surrounding communities.
-
C.
Røst parish
Røst parish is a Church of Norway parish serving the small island community of Røst in Nordland county.
-
D.
Oppstad parish
Oppstad parish is a local Church of Norway parish serving the community within the municipality of Sør-Odal in Innlandet county.
-
E.
Sogndal parish
Sogndal parish is a Church of Norway parish serving the local community in and around the village of Sogndal in Vestland county.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6402763b8819099e535979f094f9d |
completed | April 20, 2026, 3:03 p.m. |
Created at: April 10, 2026, 1:42 p.m.