Triple

T17509563
Position Surface form Disambiguated ID Type / Status
Subject Archbishopric of Novgorod E426414 entity
Predicate laterSubordinateTo P47649 FINISHED
Object Metropolitan of Moscow — 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: Metropolitan of Moscow | Statement: [Archbishopric of Novgorod, laterSubordinateTo, Metropolitan of Moscow]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Metropolitan of Moscow
Context triple: [Archbishopric of Novgorod, laterSubordinateTo, Metropolitan of Moscow]
  • A. Metropolitan of Novgorod
    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.
  • B. 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.
  • 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 Kazan
    The Metropolitan of Kazan is a senior bishop in the Russian Orthodox Church overseeing the historic Kazan diocese, a role once held by the future Patriarch Hermogenes.
  • E. Patriarch Ignatius of Moscow
    Patriarch Ignatius of Moscow was a late 16th-century head of the Russian Orthodox Church whose short and controversial tenure occurred on the eve of Russia’s Time of Troubles.
  • 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 Moscow
Target entity description: The Metropolitan of Moscow was the leading bishop and head of the Russian Orthodox Church centered in Moscow, holding major religious and political influence in medieval and early modern Russia.
  • A. Metropolitan of Novgorod
    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.
  • B. 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.
  • 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 Kazan
    The Metropolitan of Kazan is a senior bishop in the Russian Orthodox Church overseeing the historic Kazan diocese, a role once held by the future Patriarch Hermogenes.
  • E. Patriarch Ignatius of Moscow
    Patriarch Ignatius of Moscow was a late 16th-century head of the Russian Orthodox Church whose short and controversial tenure occurred on the eve of Russia’s Time of Troubles.
  • F. None of above. chosen

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_69d889dd9164819087b1dc3c9240c870 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e4525a43208190b8728214767428c0 completed April 19, 2026, 3:56 a.m.
Created at: April 10, 2026, 5:48 a.m.