Triple
T4445580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Alexander Nevsky Cathedral, Sofia |
E96276
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bulgarian Orthodox cathedral |
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: Bulgarian Orthodox cathedral Context triple: [St. Alexander Nevsky Cathedral, Sofia, instanceOf, Bulgarian Orthodox cathedral]
-
A.
organ of the Bulgarian Orthodox Church
An organ of the Bulgarian Orthodox Church is an official institutional body or administrative unit that performs specific religious, governance, or support functions within the Church’s hierarchical structure.
-
B.
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.
-
C.
Catholic cathedral
A Catholic cathedral is a large, often architecturally grand church that serves as the central place of worship and administrative seat (cathedra) of a bishop within a Catholic diocese.
-
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.
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.
- 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:32 p.m.