Triple
T14816985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Randaberg |
E348342
|
entity |
| Predicate | hasParish |
P35
|
FINISHED |
| Object |
Randaberg parish
Randaberg parish is a Church of Norway parish serving the local Lutheran congregation in the municipality of Randaberg in Rogaland county, Norway.
|
E1122521
|
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: Randaberg parish | Statement: [Randaberg, hasParish, Randaberg parish]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Randaberg parish Context triple: [Randaberg, hasParish, Randaberg parish]
-
A.
Ringebu parish
Ringebu parish is a local Church of Norway parish serving the community within Ringebu municipality in Innlandet county.
-
B.
Rygge parish
Rygge parish is a Church of Norway parish serving the local community in the Rygge area of Østfold, Norway.
-
C.
Stange parish
Stange parish is a Church of Norway parish serving the local Lutheran congregation in the Stange area of Innlandet county, Norway.
-
D.
Mykland parish
Mykland parish is a Church of Norway parish community in Norway centered around Mykland Church and serving the surrounding rural area.
-
E.
Sandvollan parish
Sandvollan parish is a local Church of Norway parish serving the Sandvollan area within the municipality of Inderøy in Trøndelag 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: Randaberg parish Triple: [Randaberg, hasParish, Randaberg parish]
Generated description
Randaberg parish is a Church of Norway parish serving the local Lutheran congregation in the municipality of Randaberg in Rogaland county, Norway.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Randaberg parish Target entity description: Randaberg parish is a Church of Norway parish serving the local Lutheran congregation in the municipality of Randaberg in Rogaland county, Norway.
-
A.
Ringebu parish
Ringebu parish is a local Church of Norway parish serving the community within Ringebu municipality in Innlandet county.
-
B.
Rygge parish
Rygge parish is a Church of Norway parish serving the local community in the Rygge area of Østfold, Norway.
-
C.
Stange parish
Stange parish is a Church of Norway parish serving the local Lutheran congregation in the Stange area of Innlandet county, Norway.
-
D.
Mykland parish
Mykland parish is a Church of Norway parish community in Norway centered around Mykland Church and serving the surrounding rural area.
-
E.
Sandvollan parish
Sandvollan parish is a local Church of Norway parish serving the Sandvollan area within the municipality of Inderøy in Trøndelag 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decfe2c1ec81908b3dff7a5d0e85d0 |
completed | April 14, 2026, 11:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe3897691c819085ef89480e730723 |
completed | May 8, 2026, 7:25 p.m. |
| NEDg | Description generation | batch_69fe5178e8b481909c88ee7db29f037c |
completed | May 8, 2026, 9:11 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69fe5217512c8190b0cea476f4b95007 |
completed | May 8, 2026, 9:13 p.m. |
Created at: April 10, 2026, 1:50 a.m.