Triple

T18278708
Position Surface form Disambiguated ID Type / Status
Subject Roman Catholic Diocese of Trier E437806 entity
Predicate formerPoliticalRole P12169 FINISHED
Object Prince-Bishopric of Trier 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 Trier | Statement: [Roman Catholic Diocese of Trier, formerPoliticalRole, Prince-Bishopric of Trier]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Prince-Bishopric of Trier
Context triple: [Roman Catholic Diocese of Trier, formerPoliticalRole, Prince-Bishopric of Trier]
  • A. Prince-Archbishopric of Trier
    The Prince-Archbishopric of Trier was an influential ecclesiastical principality of the Holy Roman Empire whose archbishop served as one of the empire’s 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 Strasbourg
    The Prince-Bishopric of Strasbourg was an ecclesiastical principality of the Holy Roman Empire centered on the city of Strasbourg, ruled by its bishop as both a spiritual and secular prince.
  • D. Bishopric of Cologne
    The Bishopric of Cologne was a significant ecclesiastical principality of the Holy Roman Empire centered on the city of Cologne, ruled by powerful prince-bishops who held both spiritual and temporal authority.
  • E. Bishopric of Aachen
    The Bishopric of Aachen was a historical ecclesiastical principality in the Holy Roman Empire centered on the city of Aachen, an important religious and political hub in medieval Europe.
  • 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 Trier
Target entity description: The Prince-Bishopric of Trier was an influential ecclesiastical principality of the Holy Roman Empire, ruled by the archbishop of Trier as both a spiritual leader and secular prince.
  • A. Prince-Archbishopric of Trier chosen
    The Prince-Archbishopric of Trier was an influential ecclesiastical principality of the Holy Roman Empire whose archbishop served as one of the empire’s 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 Strasbourg
    The Prince-Bishopric of Strasbourg was an ecclesiastical principality of the Holy Roman Empire centered on the city of Strasbourg, ruled by its bishop as both a spiritual and secular prince.
  • D. Bishopric of Cologne
    The Bishopric of Cologne was a significant ecclesiastical principality of the Holy Roman Empire centered on the city of Cologne, ruled by powerful prince-bishops who held both spiritual and temporal authority.
  • E. Bishopric of Aachen
    The Bishopric of Aachen was a historical ecclesiastical principality in the Holy Roman Empire centered on the city of Aachen, an important religious and political hub in medieval Europe.
  • 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_69d8b914530c8190b4474d862a2b2a1b completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e50054d1dc8190b31d02f617256e9d completed April 19, 2026, 4:18 p.m.
Created at: April 10, 2026, 10:34 a.m.