Triple
T9282256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palatine Chapel |
E223096
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Carolingian architecture |
C27127
|
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: Carolingian architecture Context triple: [Palatine Chapel, instanceOf, Carolingian architecture]
-
A.
medieval church
A medieval church is a religious building from the Middle Ages, typically characterized by stone construction, vaulted ceilings, stained glass windows, and architectural styles such as Romanesque or Gothic, serving as a center for worship and community life.
-
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.
Romanesque church building
A Romanesque church building is a medieval Christian structure characterized by thick stone walls, rounded arches, sturdy piers, small windows, and a fortress-like, monumental appearance.
-
D.
Carolingian intellectual
A Carolingian intellectual is a learned figure of the 8th–9th century Frankish realm who engaged in the study, preservation, and reform of classical, Christian, and legal texts to support the cultural and administrative renewal of the Carolingian Empire.
-
E.
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.
- 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_69ca842123588190b3f2e1a69037d141 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:34 p.m.