Triple
T14333915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prussian Baroque |
E355421
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variant of Baroque architecture |
C25683
|
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: regional variant of Baroque architecture Context triple: [Prussian Baroque, instanceOf, regional variant of Baroque architecture]
-
A.
Baroque architecture style
chosen
Baroque architecture style is a highly ornate and dramatic European architectural movement characterized by dynamic forms, bold contrasts of light and shadow, rich decoration, and a strong sense of movement and grandeur.
-
B.
Baroque building
A Baroque building is an architecturally elaborate structure characterized by dramatic forms, rich ornamentation, dynamic curves, and a strong emphasis on grandeur and theatrical visual effects.
-
C.
Baroque pavilion
A Baroque pavilion is an ornate, freestanding garden or park structure characterized by dynamic forms, rich decoration, and theatrical spatial effects typical of Baroque architecture.
-
D.
Baroque church building
A Baroque church building is a richly ornamented, theatrically designed place of Christian worship characterized by dynamic forms, dramatic light, and elaborate decoration intended to inspire awe and emotional devotion.
-
E.
Mannerist building
A Mannerist building is an architectural structure characterized by deliberate distortion, tension, and playful manipulation of classical forms, proportions, and conventions to create visual complexity and expressive effect.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:13 a.m.