Triple
T13798590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ringsaker |
E331578
|
entity |
| Predicate | hasParish |
P35
|
FINISHED |
| Object |
Brøttum parish
Brøttum parish is a Church of Norway parish serving the rural community of Brøttum in Ringsaker municipality in Innlandet county.
|
E1061950
|
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: Brøttum parish | Statement: [Ringsaker, hasParish, Brøttum parish]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brøttum parish Context triple: [Ringsaker, hasParish, Brøttum parish]
-
A.
Bremsnes parish
Bremsnes parish is a Church of Norway parish community centered around Bremsnes Church on the island of Averøya in Møre og Romsdal county, Norway.
-
B.
Rygge parish
Rygge parish is a Church of Norway parish serving the local community in the Rygge area of Østfold, Norway.
-
C.
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.
-
D.
Vestfossen parish
Vestfossen parish is a local Church of Norway parish centered on the village of Vestfossen in the municipality of Øvre Eiker in Buskerud, Norway.
-
E.
Røst parish
Røst parish is a Church of Norway parish serving the small island community of Røst in Nordland county.
- 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: Brøttum parish Triple: [Ringsaker, hasParish, Brøttum parish]
Generated description
Brøttum parish is a Church of Norway parish serving the rural community of Brøttum in Ringsaker municipality in Innlandet county.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Brøttum parish Target entity description: Brøttum parish is a Church of Norway parish serving the rural community of Brøttum in Ringsaker municipality in Innlandet county.
-
A.
Bremsnes parish
Bremsnes parish is a Church of Norway parish community centered around Bremsnes Church on the island of Averøya in Møre og Romsdal county, Norway.
-
B.
Rygge parish
Rygge parish is a Church of Norway parish serving the local community in the Rygge area of Østfold, Norway.
-
C.
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.
-
D.
Vestfossen parish
Vestfossen parish is a local Church of Norway parish centered on the village of Vestfossen in the municipality of Øvre Eiker in Buskerud, Norway.
-
E.
Røst parish
Røst parish is a Church of Norway parish serving the small island community of Røst in Nordland county.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de025ce9148190b23370f6a522ff7a |
completed | April 14, 2026, 9:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b086d6d48190b823ed0a4403fbc5 |
completed | May 3, 2026, 8:31 p.m. |
| NEDg | Description generation | batch_69f7b138fda88190b2b7ffb51ce02a40 |
completed | May 3, 2026, 8:34 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69f7b28ca218819097fc35042d3b278a |
completed | May 3, 2026, 8:39 p.m. |
Created at: April 9, 2026, 10:11 p.m.