Triple
T8027001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Folkekirken |
E186879
|
entity |
| Predicate | recognizesAsSupremeBishop |
P80651
|
FINISHED |
| Object | no single person |
—
|
LITERAL 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: no single person | Statement: [Folkekirken, recognizesAsSupremeBishop, no single person]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizesAsSupremeBishop Context triple: [Folkekirken, recognizesAsSupremeBishop, no single person]
-
A.
isEcclesiasticalHeadOf
Indicates that one entity serves as the highest religious or church authority for another entity.
-
B.
hasPatriarchOrMajorArchbishop
Indicates that an ecclesiastical jurisdiction is under the authority of a specific patriarch or major archbishop.
-
C.
isHolySynodOf
Indicates that an entity functions as the official governing or highest ecclesiastical council of a particular church or religious body.
-
D.
archbishopOf
Indicates that a person holds the ecclesiastical office of archbishop in relation to a specific diocese, region, or church jurisdiction.
-
E.
recognizesPopeAs
Indicates that one entity acknowledges and accepts another entity as the legitimate Pope.
- F. None of above. chosen
Provenance (4 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_69ca82ad4e2c8190a693e3c9e30fe66f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ecb00648190bb3144acf3492bb3 |
completed | March 31, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bcbbc0819094a98e7ffffb7a40 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:21 p.m.