Triple
T2969630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | facade of Santa Maria della Vittoria, Rome |
E80249
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Baroque architectural work |
C7141
|
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: Baroque architectural work Context triple: [facade of Santa Maria della Vittoria, Rome, instanceOf, Baroque architectural work]
-
A.
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.
-
B.
Renaissance architecture masterpiece
A Renaissance architecture masterpiece is a building that harmoniously combines classical proportions, symmetry, and geometric clarity with innovative engineering and rich ornamentation to embody the humanist ideals of the Renaissance.
-
C.
Baroque church
A Baroque church is a richly ornamented Christian worship building characterized by dramatic spatial compositions, dynamic forms, and lavish decorative elements designed to evoke emotional and spiritual awe.
-
D.
Baroque art
Baroque art is a highly dramatic, emotionally charged style of 17th-century European art characterized by dynamic movement, strong contrasts of light and shadow, and elaborate ornamentation designed to evoke awe and devotion.
-
E.
architectural work
chosen
An architectural work is a designed and constructed building or structure that integrates functional, aesthetic, and technical elements to shape human environments and experiences.
- 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_69ad8b14ffe881908ffed62f9595c867 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 2:58 p.m.