Triple
T2662588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic Archdiocese of Utrecht |
E54758
|
entity |
| Predicate | restoredAsArchdiocese |
P41263
|
FINISHED |
| Object | 1853 |
—
|
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: 1853 | Statement: [Roman Catholic Archdiocese of Utrecht, restoredAsArchdiocese, 1853]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restoredAsArchdiocese Context triple: [Roman Catholic Archdiocese of Utrecht, restoredAsArchdiocese, 1853]
-
A.
establishedAsDiocese
Indicates that an ecclesiastical jurisdiction was formally created or elevated to the status of a diocese.
-
B.
dioceseGovernedStart
Indicates the point in time when a particular authority or leader began governing a specific diocese.
-
C.
formerDiocese
Indicates that an entity was once a diocese but no longer holds that diocesan status.
-
D.
hasArchdiocese
Indicates that an entity serves as the archdiocese (ecclesiastical jurisdiction) associated with another entity, such as a church, region, or religious organization.
-
E.
elevatedToMajorArchepiscopalChurch
Indicates that a church has been officially raised in status to a Major Archepiscopal Church within its ecclesial tradition.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd969eff08190a206ad6424ba34d6 |
completed | March 7, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd8dd05c48190b4f90031642c4091 |
completed | March 7, 2026, 7:50 a.m. |
Created at: March 6, 2026, 9:53 p.m.