Triple

T31364071
Position Surface form Disambiguated ID Type / Status
Subject Kazan Diocese E799956 entity
Predicate isPartOfChurchProvince P3089 FINISHED
Object Moscow Patriarchate NE NERFINISHED

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: Moscow Patriarchate | Statement: [Kazan Diocese, isPartOfChurchProvince, Moscow Patriarchate]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isPartOfChurchProvince
Context triple: [Kazan Diocese, isPartOfChurchProvince, Moscow Patriarchate]
  • A. churchProvinceIncludes
    Indicates that a church province encompasses or contains a particular subordinate ecclesiastical unit or area.
  • B. isTitularChurchOf
    Indicates that a particular church holds the official honorary title associated with a specific cardinal or ecclesiastical office.
  • C. hasClericalProvince
    Indicates that one ecclesiastical jurisdiction or entity is part of, or belongs to, a specific clerical (church) province.
  • D. cathedralProvince
    Indicates the ecclesiastical province to which a cathedral (or its diocese) belongs within a church hierarchy.
  • E. churchProvince chosen
    Indicates that one entity is an ecclesiastical province to which the other entity (typically a church jurisdiction or diocese) belongs or is administratively subordinate.
  • 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_69f224e6b7448190ac6bf97ad7364160 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69fe6b7c785c8190aaab06019f571434 completed May 8, 2026, 11:02 p.m.
PD Predicate disambiguation batch_69fe68edef20819081c77f9607b944dd completed May 8, 2026, 10:51 p.m.
Created at: April 29, 2026, 9:18 p.m.