Triple
T30825849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Königsberg Stock Exchange |
E785059
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | neoclassical architecture building |
C29660
|
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: neoclassical architecture building Context triple: [Königsberg Stock Exchange, instanceOf, neoclassical architecture building]
-
A.
neoclassical government building
A neoclassical government building is a formal public structure characterized by symmetrical design, grand columns, pediments, and classical Greek and Roman architectural elements that convey authority, stability, and civic importance.
-
B.
classical-style building
chosen
A classical-style building is a structure characterized by symmetry, proportion, and the use of traditional Greco-Roman elements such as columns, pediments, and decorative moldings.
-
C.
neoclassical temple
A neoclassical temple is a monumental structure inspired by ancient Greek and Roman religious architecture, characterized by symmetrical form, columned porticoes, and restrained classical ornamentation.
-
D.
neoclassical palace
A neoclassical palace is a grand, formal residence or governmental building designed in the neoclassical style, characterized by symmetry, classical columns, pediments, and restrained decorative elements inspired by ancient Greek and Roman architecture.
-
E.
neoclassical pavilion
A neoclassical pavilion is a small, freestanding structure characterized by symmetrical form, classical columns, and restrained ornamentation, often set within a garden or landscape as an elegant focal point or retreat.
- 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_69f224b6642481909e8d701de2cd1a53 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:44 p.m.