Triple
T20442652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heddal Stave Church |
E501433
|
entity |
| Predicate | hasParish |
P35
|
FINISHED |
| Object | Heddal 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: Heddal parish | Statement: [Heddal Stave Church, hasParish, Heddal parish]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heddal parish Context triple: [Heddal Stave Church, hasParish, Heddal parish]
-
A.
Hemsedal parish
Hemsedal parish is a local Church of Norway parish serving the community of Hemsedal in Viken county, Norway.
-
B.
Hyllestad parish
Hyllestad parish is a local Church of Norway parish serving the community within Hyllestad Municipality in western Norway.
-
C.
Haug parish
Haug parish is a local Church of Norway parish serving part of the Ringerike area in Buskerud, Norway.
-
D.
Heddal
chosen
Heddal is a village in Notodden Municipality in Vestfold og Telemark county, Norway, best known for the large medieval Heddal Stave Church.
-
E.
Alstahaug parish
Alstahaug parish is a Church of Norway parish serving the local community in the Alstahaug area of Nordland 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_69e0b4ac0a1c81908845d0f8a56abce8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e685f3b794819080745b135a305ba7 |
completed | April 20, 2026, 8 p.m. |
Created at: April 16, 2026, 11:32 a.m.