Triple
T22326662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standardized designs for Norwegian rural churches |
E551918
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | church building typology |
C26677
|
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: church building typology Context triple: [Standardized designs for Norwegian rural churches, instanceOf, church building typology]
-
A.
church building type
chosen
A church building type is a category of architectural design specifically intended for Christian worship, characterized by particular spatial layouts, symbolic elements, and functional features that support liturgical practices and congregational gatherings.
-
B.
particular church structure
A particular church structure is an individual, organized Christian community or congregation, with its own governance and physical or communal framework, that forms a distinct unit within the broader Church.
-
C.
cathedral design
Cathedral design is the conceptual planning and organization of a cathedral’s spatial layout, structural system, aesthetic elements, and symbolic features to support liturgical functions and spiritual experience.
-
D.
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.
-
E.
contemporary church building
A contemporary church building is a modern place of Christian worship that integrates current architectural styles, materials, and technologies while accommodating liturgical functions and community activities.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:42 p.m.