Triple
T1716723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of the Holy Apostles |
E37306
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine church |
C6309
|
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: Byzantine church Context triple: [Church of the Holy Apostles, instanceOf, Byzantine church]
-
A.
Eastern Orthodox church
chosen
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.
-
B.
Oriental Orthodox Church
The Oriental Orthodox Church is a communion of Eastern Christian churches that reject the Council of Chalcedon and share a common Miaphysite Christology, liturgical tradition, and apostolic heritage.
-
C.
Eastern Orthodox Christian
An Eastern Orthodox Christian is a follower of the Eastern Orthodox Church who adheres to its ancient liturgical traditions, theology, and spiritual practices centered on the Holy Trinity, the sacraments, and the continuity of the early Christian faith.
-
D.
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.
-
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.
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_69a8861912dc8190931af43b4b9158a7 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:30 p.m.