Triple
T10428047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rygge |
E245836
|
entity |
| Predicate | locatedInEcclesiasticalTerritorialEntity |
P40
|
FINISHED |
| Object | Rygge parish |
E861489
|
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: Rygge parish | Statement: [Rygge, locatedInEcclesiasticalTerritorialEntity, Rygge parish]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rygge parish Context triple: [Rygge, locatedInEcclesiasticalTerritorialEntity, Rygge parish]
-
A.
Rygge parish
chosen
Rygge parish is a Church of Norway parish serving the local community in the Rygge area of Østfold, Norway.
-
B.
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.
-
C.
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.
-
D.
Røra parish
Røra parish is a Church of Norway parish serving the local community within the municipality of Inderøy in Trøndelag county, Norway.
-
E.
Haug parish
Haug parish is a local Church of Norway parish serving part of the Ringerike area in Buskerud, Norway.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea4a7dcc81909a830e08656a1c0c |
completed | April 7, 2026, 11:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d87ea554888190bf2ef31e33c0ff14 |
completed | April 10, 2026, 4:37 a.m. |
Created at: April 6, 2026, 12:13 p.m.