Triple
T15062071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of the Holy Virgin Hodegetria |
E379652
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine-style church |
C34419
|
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-style church Context triple: [Church of the Holy Virgin Hodegetria, instanceOf, Byzantine-style church]
-
A.
Byzantine basilica
A Byzantine basilica is a Christian church building that combines the longitudinal basilican plan with characteristic Byzantine features such as domes, rich mosaics, and elaborate centralized spaces.
-
B.
Orthodox church building
chosen
An Orthodox church building is a sacred Christian structure designed for Eastern Orthodox worship, typically featuring a domed roof, iconostasis, and richly decorated icons that facilitate liturgical rites and communal prayer.
-
C.
Neo-Byzantine building
A Neo-Byzantine building is a structure designed in a revival style that draws on medieval Byzantine architecture, featuring elements such as domes, rounded arches, rich ornamentation, and often elaborate brick or stonework.
-
D.
Christian basilica
A Christian basilica is a large, rectangular church building, often with a central nave, side aisles, and an apse, originally adapted from Roman civic architecture for Christian worship and liturgical gatherings.
-
E.
Georgian Orthodox church building
A Georgian Orthodox church building is a Christian worship structure associated with the Georgian Orthodox Church, typically featuring traditional Georgian ecclesiastical architecture, iconography, and liturgical spaces.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3:02 a.m.