Triple

T36493619
Position Surface form Disambiguated ID Type / Status
Subject Eparchy of Făgăraș E899117 entity
Predicate instanceOf P0 FINISHED
Object Catholic eparchy C64787 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: Catholic eparchy
Context triple: [Eparchy of Făgăraș, instanceOf, Catholic eparchy]
  • A. Byzantine Catholic eparchy
    A Byzantine Catholic eparchy is a territorial jurisdiction of the Eastern Catholic Church, governed by a bishop (eparch) who oversees the pastoral, liturgical, and administrative life of Byzantine-rite faithful in communion with the Pope.
  • B. Maronite Catholic eparchy
    A Maronite Catholic eparchy is a territorial jurisdiction of the Maronite Church, governed by a bishop (eparch) who oversees the pastoral care, administration, and liturgical life of Maronite Catholics within its boundaries.
  • C. Syro-Malankara Catholic eparchy
    A Syro-Malankara Catholic eparchy is a territorial jurisdiction of the Syro-Malankara Catholic Church, headed by a bishop, responsible for the pastoral care, administration, and liturgical life of the faithful within its defined region.
  • D. Ukrainian Greek Catholic archeparchy
    A Ukrainian Greek Catholic archeparchy is a principal ecclesiastical jurisdiction of the Ukrainian Greek Catholic Church, headed by an archeparch and overseeing multiple eparchies within a defined territory.
  • E. Maronite Catholic archeparchy
    A Maronite Catholic archeparchy is a principal ecclesiastical jurisdiction of the Maronite Church, headed by an archeparch (archbishop), overseeing multiple eparchies and parishes within a defined territory in full communion with the Pope.
  • 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_69f76e5ad4588190bdbce60c52fbb785 completed May 3, 2026, 3:48 p.m.
Created at: May 3, 2026, 4:10 p.m.