Triple
T735631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richardsonian Romanesque |
E14924
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Romanesque Revival architecture |
C821
|
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: Romanesque Revival architecture Context triple: [Richardsonian Romanesque, instanceOf, Romanesque Revival architecture]
-
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.
architectural style
chosen
An architectural style is a distinctive set of design principles, forms, materials, and decorative elements that characterize the built works of a particular period, region, culture, or movement.
-
C.
Beaux-Arts building
A Beaux-Arts building is a grand, formally composed structure characterized by classical symmetry, rich ornamentation, and monumental scale, reflecting the academic architectural principles of the École des Beaux-Arts in Paris.
-
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.
Roman Catholic basilica
A Roman Catholic basilica is a church building granted special ceremonial privileges and honorific status by the Pope, often distinguished by its historical, spiritual, or architectural significance.
- 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_69a4934d9930819099eed80096b0597d |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:37 p.m.