Triple
T25734449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ratzeburg Cathedral |
E645336
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | brick Gothic and Romanesque structure |
C26076
|
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: brick Gothic and Romanesque structure Context triple: [Ratzeburg Cathedral, instanceOf, brick Gothic and Romanesque structure]
-
A.
Romanesque-Byzantine church
A Romanesque-Byzantine church is a religious building that combines the heavy, rounded-arch masonry and fortress-like massing of Romanesque architecture with the domes, mosaics, and centralized plans characteristic of Byzantine design.
-
B.
brick Gothic architecture
chosen
Brick Gothic architecture is a medieval Northern European style characterized by the use of exposed red brick, pointed arches, and simplified Gothic forms adapted to regions lacking natural stone.
-
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.
Gothic building
A Gothic building is a tall, often stone structure characterized by pointed arches, ribbed vaults, flying buttresses, and large stained-glass windows that create a dramatic, vertically oriented aesthetic.
-
E.
Flamboyant Gothic architecture
Flamboyant Gothic architecture is a late Gothic style characterized by intricate, flame-like tracery, highly ornate stonework, and elaborate decorative patterns that create a sense of dynamic movement and visual richness.
- 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_69e77e85254081908d79ee4e8715f283 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 11:22 p.m.