Triple
T8530481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Roskilde |
E201932
|
entity |
| Predicate | establishedAsCurrentDiocese |
P83169
|
FINISHED |
| Object | 1922 |
—
|
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: 1922 | Statement: [Diocese of Roskilde, establishedAsCurrentDiocese, 1922]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsCurrentDiocese Context triple: [Diocese of Roskilde, establishedAsCurrentDiocese, 1922]
-
A.
establishedAsDiocese
Indicates that an ecclesiastical jurisdiction was formally created or elevated to the status of a diocese.
-
B.
establishedAsArchdioceseOn
Indicates that a religious jurisdiction was formally elevated to the status of an archdiocese on a specific date.
-
C.
dioceseGovernedStart
Indicates the point in time when a particular authority or leader began governing a specific diocese.
-
D.
formerDiocese
Indicates that an entity was once a diocese but no longer holds that diocesan status.
-
E.
restoredAsArchdiocese
Indicates that an ecclesiastical jurisdiction, previously reduced or altered in status, has been returned to the rank and authority of an archdiocese.
- 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_69ca83228b24819085d22e7dc99f5d94 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe67546248190b359c845c0161ad3 |
completed | March 31, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69cbd111bf988190be98c92a607c6456 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:17 p.m.