Triple
T17485224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Rhine Romanesque architecture tradition |
E425761
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional architectural style |
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: regional architectural style Context triple: [Upper Rhine Romanesque architecture tradition, instanceOf, regional architectural style]
-
A.
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.
-
B.
regional variant of Art Nouveau
A regional variant of Art Nouveau is a localized adaptation of the broader Art Nouveau movement that incorporates distinctive motifs, materials, and cultural influences specific to a particular geographic area while retaining the style’s characteristic emphasis on organic forms and flowing lines.
-
C.
regional studio
A regional studio is a localized creative production space that develops and delivers media, art, or design content tailored to the cultural, economic, and audience needs of a specific geographic area.
-
D.
architectural family
An architectural family is a group of related building designs or structures that share common stylistic, functional, or structural characteristics derived from a unifying design concept or lineage.
-
E.
architectural feature
An architectural feature is a distinct structural or decorative element of a building or space that contributes to its function, aesthetics, or character.
- 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:48 a.m.