Triple

T17332949
Position Surface form Disambiguated ID Type / Status
Subject Patriarch Alexy II of Moscow E420859 entity
Predicate heldTitle P8 FINISHED
Object Metropolitan of Novgorod — NE ONNED1

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: Metropolitan of Novgorod | Statement: [Patriarch Alexy II of Moscow, heldTitle, Metropolitan of Novgorod]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Metropolitan of Novgorod
Context triple: [Patriarch Alexy II of Moscow, heldTitle, Metropolitan of Novgorod]
  • A. Metropolitan of Smolensk and Kaliningrad
    The Metropolitan of Smolensk and Kaliningrad is a senior bishopric in the Russian Orthodox Church overseeing the dioceses around the cities of Smolensk and Kaliningrad in western Russia.
  • B. Archbishop of Yaroslavl
    The Archbishop of Yaroslavl is a senior bishop in the Russian Orthodox Church overseeing the Yaroslavl diocese, a role once held by the future Patriarch Tikhon of Moscow.
  • C. Metropolitan of Siberia
    The Metropolitan of Siberia was a high-ranking bishopric of the Russian Orthodox Church overseeing ecclesiastical affairs across the vast Siberian region.
  • D. Metropolitan of Saint Petersburg and Ladoga (historically)
    The Metropolitan of Saint Petersburg and Ladoga (historically) was a leading hierarch of the Russian Orthodox Church overseeing the ecclesiastical administration of the Saint Petersburg region.
  • E. Metropolitan of Ruse
    The Metropolitan of Ruse is a senior Eastern Orthodox bishop overseeing the Diocese of Ruse within the Bulgarian Orthodox Church.
  • 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: Metropolitan of Novgorod
Target entity description: The Metropolitan of Novgorod is a senior bishopric in the Russian Orthodox Church historically responsible for overseeing the influential Novgorod region and its ecclesiastical affairs.
  • A. Metropolitan of Smolensk and Kaliningrad
    The Metropolitan of Smolensk and Kaliningrad is a senior bishopric in the Russian Orthodox Church overseeing the dioceses around the cities of Smolensk and Kaliningrad in western Russia.
  • B. Archbishop of Yaroslavl
    The Archbishop of Yaroslavl is a senior bishop in the Russian Orthodox Church overseeing the Yaroslavl diocese, a role once held by the future Patriarch Tikhon of Moscow.
  • C. Metropolitan of Siberia
    The Metropolitan of Siberia was a high-ranking bishopric of the Russian Orthodox Church overseeing ecclesiastical affairs across the vast Siberian region.
  • D. Metropolitan of Saint Petersburg and Ladoga (historically)
    The Metropolitan of Saint Petersburg and Ladoga (historically) was a leading hierarch of the Russian Orthodox Church overseeing the ecclesiastical administration of the Saint Petersburg region.
  • E. Metropolitan of Ruse
    The Metropolitan of Ruse is a senior Eastern Orthodox bishop overseeing the Diocese of Ruse within the Bulgarian Orthodox Church.
  • F. None of above. chosen

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_69d889d3adc881909319f1edb8d2a956 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43a0fa57881909071fd395b3d46c4 completed April 19, 2026, 2:12 a.m.
NED1 Entity disambiguation (via context triple) batch_6a019550d3bc8190bda76e83edc81063 finalizing May 11, 2026, 8:37 a.m.
Created at: April 10, 2026, 5:43 a.m.