Triple

T4218733
Position Surface form Disambiguated ID Type / Status
Subject Holy Synod of the Bulgarian Orthodox Church E94285 entity
Predicate instanceOf P0 FINISHED
Object organ of the Bulgarian Orthodox Church C15361 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07 
Target class: organ of the Bulgarian Orthodox Church
Context triple: [Holy Synod of the Bulgarian Orthodox Church, instanceOf, organ of the Bulgarian Orthodox Church]
  • A. organ of the Serbian Orthodox Church
    An organ of the Serbian Orthodox Church is an official institutional body or administrative unit that performs specific religious, governance, or organizational functions within the Church’s hierarchical structure.
  • B. organ of the Russian Orthodox Church
    An organ of the Russian Orthodox Church is a formal institutional body or administrative unit within the Church that carries out specific religious, governance, or organizational functions under its canonical authority.
  • C. Eastern Orthodox bishop
    An Eastern Orthodox bishop is a high-ranking cleric who holds apostolic succession and oversees the spiritual, liturgical, and administrative life of a diocese within the Eastern Orthodox Church.
  • D. Byzantine Rite Church
    A Byzantine Rite Church is a Christian church that follows the liturgical, theological, and spiritual traditions of the Byzantine rite, characterized by its Eastern Christian worship, iconography, and ecclesiastical customs.
  • E. Russian Orthodox church
    A Russian Orthodox church is a Christian religious building belonging to the Russian Orthodox tradition, characterized by its distinctive onion domes, iconostasis, and liturgical practices rooted in Eastern Orthodoxy.
  • F. None of above. chosen

Provenance (1 batch)

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_69b3451997e08190851db4a9a588837d completed March 12, 2026, 10:58 p.m.
Created at: March 12, 2026, 11:04 p.m.