Triple
T3386629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dohány Street Synagogue |
E71317
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 19th-century religious building |
C10197
|
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: 19th-century religious building Context triple: [Dohány Street Synagogue, instanceOf, 19th-century religious building]
-
A.
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.
-
B.
Historic church
A historic church is a long-standing religious building of significant architectural, cultural, and spiritual importance that reflects the beliefs, artistry, and community life of its era.
-
C.
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.
-
D.
Romanesque Revival building
chosen
A Romanesque Revival building is a structure designed in a 19th-century historicist style that reinterprets medieval Romanesque architecture through features like round arches, heavy masonry, robust towers, and deeply recessed openings.
-
E.
17th-century church
A 17th-century church is a religious building constructed in the 1600s that typically reflects Baroque or late Renaissance architectural styles, serving as a place of Christian worship and community gathering.
- 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:14 p.m.