Triple
T38022079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armenian Catholic Patriarchal Eparchy of Beirut |
E948663
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | patriarchal 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: patriarchal eparchy Context triple: [Armenian Catholic Patriarchal Eparchy of Beirut, instanceOf, patriarchal eparchy]
-
A.
ancient patriarchate
An ancient patriarchate is a senior episcopal jurisdiction in early Christianity, historically led by a patriarch who held preeminent authority over a major Christian center and its surrounding territories.
-
B.
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.
-
C.
Catholic eparchy
chosen
A Catholic eparchy is a territorial jurisdiction of the Eastern Catholic Churches, equivalent to a diocese, governed by a bishop (eparch) who oversees the pastoral care, administration, and spiritual life of the faithful within its boundaries.
-
D.
Catholic patriarchate
A Catholic patriarchate is a major ecclesiastical jurisdiction in the Catholic Church, headed by a patriarch who holds a primatial rank and authority over a particular rite or territory within the universal Church.
-
E.
patriarchal curia
A patriarchal curia is the central administrative and advisory body that assists a patriarch in governing a particular Eastern Catholic Church or patriarchal jurisdiction.
- F. None of above.
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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.