Triple
T2654910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coptic Catholic Church |
E53985
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Alexandrian Rite church |
C9225
|
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: Alexandrian Rite church Context triple: [Coptic Catholic Church, instanceOf, Alexandrian Rite church]
-
A.
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.
-
B.
Maronite Catholic church
A Maronite Catholic church is a place of worship belonging to the Maronite Church, an Eastern Catholic Church in full communion with Rome, that follows the West Syriac liturgical tradition and preserves distinct Antiochene spiritual and cultural heritage.
-
C.
Oriental church
chosen
An Oriental church is a Christian church belonging to the family of Eastern Christian traditions, particularly those that developed in the Middle East and surrounding regions, often with distinct liturgies, languages, and theological emphases from Western Christianity.
-
D.
Eastern Orthodox church
An Eastern Orthodox church is a Christian place of worship characterized by its adherence to Eastern Orthodox theology and liturgy, often featuring domes, icons, and a richly decorated interior focused on the Divine Liturgy.
-
E.
Roman Catholic church
A Roman Catholic church is a Christian place of worship that serves as a local community’s center for liturgy, sacraments, and prayer within the Roman Catholic tradition.
- 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_69ab495e192081909c77b622e8e7e15a |
completed | March 6, 2026, 9:38 p.m. |
Created at: March 6, 2026, 9:53 p.m.