Triple
T17485191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic Diocese of Mainz |
E425760
|
entity |
| Predicate | historicalStatus |
P339
|
FINISHED |
| Object | Prince-Bishopric of Mainz |
—
|
NE NERFINISHED |
How this triple was built (3 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: Prince-Bishopric of Mainz | Statement: [Roman Catholic Diocese of Mainz, historicalStatus, Prince-Bishopric of Mainz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Prince-Bishopric of Mainz Context triple: [Roman Catholic Diocese of Mainz, historicalStatus, Prince-Bishopric of Mainz]
-
A.
Prince-Archbishopric of Mainz
The Prince-Archbishopric of Mainz was a powerful ecclesiastical principality of the Holy Roman Empire whose archbishop served as archchancellor and one of the leading prince-electors.
-
B.
Prince-Bishopric of Speyer
The Prince-Bishopric of Speyer was an ecclesiastical principality of the Holy Roman Empire centered on the city of Speyer, ruled by a prince-bishop who held both spiritual and temporal authority.
-
C.
Prince-Bishopric of Worms
The Prince-Bishopric of Worms was an ecclesiastical principality of the Holy Roman Empire centered on the city of Worms, ruled by a prince-bishop who held both spiritual and temporal authority.
-
D.
Prince-Bishopric of Fulda
The Prince-Bishopric of Fulda was an ecclesiastical principality of the Holy Roman Empire centered on the wealthy and influential Fulda Abbey in what is now central Germany.
-
E.
Prince-Bishopric of Würzburg
The Prince-Bishopric of Würzburg was an ecclesiastical principality within the Holy Roman Empire, ruled by a Catholic prince-bishop and centered on the city of Würzburg in Franconia.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Prince-Bishopric of Mainz Target entity description: The Prince-Bishopric of Mainz was a powerful ecclesiastical principality within the Holy Roman Empire whose archbishop served as archchancellor of Germany and one of the empire’s leading prince-electors.
-
A.
Prince-Archbishopric of Mainz
chosen
The Prince-Archbishopric of Mainz was a powerful ecclesiastical principality of the Holy Roman Empire whose archbishop served as archchancellor and one of the leading prince-electors.
-
B.
Prince-Bishopric of Speyer
The Prince-Bishopric of Speyer was an ecclesiastical principality of the Holy Roman Empire centered on the city of Speyer, ruled by a prince-bishop who held both spiritual and temporal authority.
-
C.
Prince-Bishopric of Worms
The Prince-Bishopric of Worms was an ecclesiastical principality of the Holy Roman Empire centered on the city of Worms, ruled by a prince-bishop who held both spiritual and temporal authority.
-
D.
Prince-Bishopric of Fulda
The Prince-Bishopric of Fulda was an ecclesiastical principality of the Holy Roman Empire centered on the wealthy and influential Fulda Abbey in what is now central Germany.
-
E.
Prince-Bishopric of Würzburg
The Prince-Bishopric of Würzburg was an ecclesiastical principality within the Holy Roman Empire, ruled by a Catholic prince-bishop and centered on the city of Würzburg in Franconia.
- F. None of above.
Provenance (2 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. |
Created at: April 10, 2026, 5:48 a.m.