Triple
T10553242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Urbanus Church |
E249007
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | neo-Gothic church building |
C4327
|
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: neo-Gothic church building Context triple: [St. Urbanus Church, instanceOf, neo-Gothic church building]
-
A.
Gothic Revival church
chosen
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.
-
B.
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.
-
C.
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.
-
D.
neo-Romanesque church
A neo-Romanesque church is a religious building designed in a 19th- or early 20th-century revival of Romanesque architecture, featuring rounded arches, thick walls, sturdy piers, and often simple, massive forms.
-
E.
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.
- 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:34 p.m.