Triple
T8367930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Ribe |
E197380
|
entity |
| Predicate | isPartOf |
P10
|
FINISHED |
| Object | Folkekirken |
E186879
|
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: Folkekirken | Statement: [Diocese of Ribe, isPartOf, Folkekirken]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Folkekirken Context triple: [Diocese of Ribe, isPartOf, Folkekirken]
-
A.
Folkekirken
chosen
Folkekirken is the national Evangelical Lutheran church of Denmark and the largest Christian denomination in the country.
-
B.
Ris Church
Ris Church is a Norwegian church in Oslo, best known as one of architect Arnstein Arneberg’s significant ecclesiastical designs.
-
C.
Fogn Church
Fogn Church is a parish church serving the local community on the island of Fogn in Finnøy, Norway.
-
D.
Sankt Catharinæ Church
Sankt Catharinæ Church is a historic medieval church in Hjørring, Denmark, noted for its traditional architecture and cultural significance in the region.
-
E.
Viby Church
Viby Church is a historic parish church serving the community of Viby J in Denmark.
- 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_69ca82f56730819080cec5d991c76f4c |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb808e56fc81908b5d37482f29452d |
completed | March 31, 2026, 8:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cdc7929e388190b35505378d0cf653 |
completed | April 2, 2026, 1:34 a.m. |
Created at: March 30, 2026, 6 p.m.