Triple
T25954444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Justinianic building program |
E654056
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine architectural initiative |
C50149
|
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 architectural initiative Context triple: [Justinianic building program, instanceOf, Byzantine architectural initiative]
-
A.
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.
-
B.
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.
-
C.
Byzantine mosaic cycle
A Byzantine mosaic cycle is a coordinated series of mosaic images, typically adorning the walls, vaults, and domes of a church, that together narrate sacred stories or express a unified theological program.
-
D.
Byzantine reform movement
The Byzantine reform movement was a series of religious, administrative, and military initiatives within the Byzantine Empire aimed at strengthening imperial authority, purifying religious practice, and restoring social and economic stability in response to internal decay and external threats.
-
E.
Byzantine theme
A Byzantine theme was a military-administrative district of the Byzantine Empire, governed by a strategos who oversaw both civil administration and regional defense.
- F. None of above. chosen
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_69e7ab40ac788190a771bc499eb1ae5f |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 8:44 a.m.