Triple
T5258826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Högalid Church |
E118768
|
entity |
| Predicate | parish |
P2739
|
FINISHED |
| Object | Högalid Parish |
E506890
|
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: Högalid Parish | Statement: [Högalid Church, parish, Högalid Parish]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Högalid Parish Context triple: [Högalid Church, parish, Högalid Parish]
-
A.
Högalid parish
chosen
Högalid parish is a Church of Sweden parish in Stockholm that encompasses the area around the prominent Högalid Church on Södermalm.
-
B.
Haug parish
Haug parish is a local Church of Norway parish serving part of the Ringerike area in Buskerud, Norway.
-
C.
Ådal parish
Ådal parish is a rural ecclesiastical and historical district within the municipality of Ringerike in Buskerud, Norway.
-
D.
Hyllestad Municipality
Hyllestad Municipality is a small coastal municipality in western Norway known for its fjord landscapes and traditional stone quarrying heritage.
-
E.
Hamar parish
Hamar parish is a Church of Norway parish serving the town and surrounding area of Hamar in Innlandet county.
- 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_69bd446978108190bb5f9c5c23d93f88 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7ba791c08190a18176feae8d1475 |
completed | March 20, 2026, 4:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf06c3945c8190874ecd184fa886a0 |
completed | March 21, 2026, 8:59 p.m. |
Created at: March 20, 2026, 1:50 p.m.