Triple
T2543135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aachen Town Hall |
E57831
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Gothic building |
C11069
|
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: Gothic building Context triple: [Aachen Town Hall, instanceOf, Gothic building]
-
A.
Gothic Revival architecture building
A Gothic Revival architecture building is a structure designed in the 19th-century revival of medieval Gothic style, characterized by pointed arches, steeply pitched roofs, ornate tracery, and vertical emphasis.
-
B.
Gothic Revival church
A Gothic Revival church is a Christian worship building designed in the 19th-century revival of medieval Gothic architecture, featuring pointed arches, ribbed vaults, and ornate tracery.
-
C.
Renaissance building
A Renaissance building is a structure characterized by symmetry, proportion, and classical elements such as columns, pilasters, arches, and domes, reflecting the revival of ancient Greek and Roman architectural principles during the 14th–17th centuries.
-
D.
Georgian church building
A Georgian church building is a Christian place of worship constructed or used during the Georgian era (1714–1830/37), typically characterized by balanced classical proportions, restrained ornamentation, and often brick or stone facades reflecting the architectural tastes of that period.
-
E.
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.
- 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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
Created at: March 6, 2026, 9:47 p.m.