Triple
T17485197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic Diocese of Mainz |
E425760
|
entity |
| Predicate | reestablishedAsDioceseInYear |
P83169
|
FINISHED |
| Object | 1802 |
—
|
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: 1802 | Statement: [Roman Catholic Diocese of Mainz, reestablishedAsDioceseInYear, 1802]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reestablishedAsDioceseInYear Context triple: [Roman Catholic Diocese of Mainz, reestablishedAsDioceseInYear, 1802]
-
A.
dioceseEstablishedBy
Indicates that a diocese was founded, created, or formally instituted by a particular person or authority.
-
B.
establishedAsArchdioceseOn
Indicates that a religious jurisdiction was formally elevated to the status of an archdiocese on a specific date.
-
C.
establishedAsDiocese
Indicates that an ecclesiastical jurisdiction was formally created or elevated to the status of a diocese.
-
D.
establishedAsCurrentDiocese
chosen
Indicates that an ecclesiastical jurisdiction was formally constituted or recognized in its present status as a diocese.
-
E.
dioceseGovernedStart
Indicates the point in time when a particular authority or leader began governing a specific diocese.
- 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451d13e208190a187b5a08fd2b5d5 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.