Triple
T23589921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catholic Church in Norway |
E582447
|
entity |
| Predicate | mainSuccessorChurch |
P96726
|
FINISHED |
| Object | Church of Norway |
—
|
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: Church of Norway | Statement: [Catholic Church in Norway, mainSuccessorChurch, Church of Norway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainSuccessorChurch Context triple: [Catholic Church in Norway, mainSuccessorChurch, Church of Norway]
-
A.
successorParish
Indicates that one parish has formally succeeded another parish, taking over its ecclesiastical role or jurisdiction.
-
B.
modernSuccessorDiocese
Indicates that one diocese is the present-day or contemporary successor to an earlier, historically related diocese.
-
C.
principalChurchOf
chosen
Indicates that one church serves as the main or most important church associated with a particular entity, such as a region, denomination, or institution.
-
D.
successorSeeCathedral
Indicates that a successor visits or observes a cathedral.
-
E.
successorReligionAtSite
Indicates that one religion historically replaced or followed another as the primary religion practiced at a specific site.
- F. None of above.
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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b03484e4819093d5c14c891f7744 |
completed | April 29, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:41 p.m.