Triple
T23069309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beitstad |
E575146
|
entity |
| Predicate | hasParish |
P35
|
FINISHED |
| Object |
Beitstad parish
Beitstad parish is a Church of Norway parish serving the rural community of Beitstad in Steinkjer municipality, Trøndelag county, Norway.
|
E1568485
|
NE FINISHED |
How this triple was built (4 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: Beitstad parish | Statement: [Beitstad, hasParish, Beitstad parish]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Beitstad parish Context triple: [Beitstad, hasParish, Beitstad parish]
-
A.
Fredrikstad parish
Fredrikstad parish is a Church of Norway parish centered in the city of Fredrikstad, serving the local Lutheran congregation and community.
-
B.
Oppstad parish
Oppstad parish is a local Church of Norway parish serving the community within the municipality of Sør-Odal in Innlandet county.
-
C.
Kornstad parish
Kornstad parish is a Church of Norway parish serving the local Lutheran congregation in the coastal area of Averøy in Møre og Romsdal county.
-
D.
Hyllestad parish
Hyllestad parish is a local Church of Norway parish serving the community within Hyllestad Municipality in western Norway.
-
E.
Fenstad parish
Fenstad parish is a local Church of Norway parish and community area within the municipality of Nes in Viken county, Norway.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Beitstad parish Triple: [Beitstad, hasParish, Beitstad parish]
Generated description
Beitstad parish is a Church of Norway parish serving the rural community of Beitstad in Steinkjer municipality, Trøndelag county, Norway.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Beitstad parish Target entity description: Beitstad parish is a Church of Norway parish serving the rural community of Beitstad in Steinkjer municipality, Trøndelag county, Norway.
-
A.
Fredrikstad parish
Fredrikstad parish is a Church of Norway parish centered in the city of Fredrikstad, serving the local Lutheran congregation and community.
-
B.
Oppstad parish
Oppstad parish is a local Church of Norway parish serving the community within the municipality of Sør-Odal in Innlandet county.
-
C.
Kornstad parish
Kornstad parish is a Church of Norway parish serving the local Lutheran congregation in the coastal area of Averøy in Møre og Romsdal county.
-
D.
Hyllestad parish
Hyllestad parish is a local Church of Norway parish serving the community within Hyllestad Municipality in western Norway.
-
E.
Fenstad parish
Fenstad parish is a local Church of Norway parish and community area within the municipality of Nes in Viken county, Norway.
- F. None of above. chosen
Provenance (5 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_69e245bd6e4c8190bb8942245b68cad5 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f189a676c08190863c034663406018 |
completed | April 29, 2026, 4:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0c0aef03e08190884fa1ba9a92baf7 |
completed | May 19, 2026, 7:02 a.m. |
| NEDg | Description generation | batch_6a0c0e82010c8190b97e9f69ab6ba138 |
completed | May 19, 2026, 7:17 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0c0ef4f6848190b149aef73c970283 |
completed | May 19, 2026, 7:19 a.m. |
Created at: April 17, 2026, 3:55 p.m.