Triple
T22997421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Røra Church |
E572539
|
entity |
| Predicate | parish |
P2739
|
FINISHED |
| Object | Røra 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: Røra parish | Statement: [Røra Church, parish, Røra parish]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Røra parish Context triple: [Røra Church, parish, Røra parish]
-
A.
Røra parish
chosen
Røra parish is a Church of Norway parish serving the local community within the municipality of Inderøy in Trøndelag 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.
Volda parish
Volda parish is a Church of Norway parish serving the local Lutheran congregation in the municipality of Volda in western Norway.
-
D.
Alstahaug parish
Alstahaug parish is a Church of Norway parish serving the local community in the Alstahaug area of Nordland county.
-
E.
Ringsaker parish
Ringsaker parish is a Church of Norway parish serving the local Lutheran congregation in the Ringsaker area of Innlandet county, Norway.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182f452b48190951fc5dde56c1bb2 |
completed | April 29, 2026, 4:03 a.m. |
Created at: April 17, 2026, 3:50 p.m.