Triple
T37815140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Empire architecture in North Carolina |
E942754
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional architectural expression |
C51711
|
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 expression Context triple: [Second Empire architecture in North Carolina, instanceOf, regional architectural expression]
-
A.
regional architecture of the United States
The regional architecture of the United States encompasses the diverse building styles, materials, and design traditions that have developed in different parts of the country in response to local climate, culture, history, and available resources.
-
B.
regional style
chosen
A regional style is a distinctive set of aesthetic, functional, or behavioral characteristics in design, art, or practice that emerges from and reflects the cultural, environmental, and historical context of a specific geographic area.
-
C.
architecturalConcept
An architecturalConcept is an abstract idea or guiding principle that informs the overall design, organization, and experiential qualities of a built environment.
-
D.
architectural style
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.
-
E.
architectural design
Architectural design is the conceptual and creative process of planning, organizing, and detailing the form, function, and aesthetics of built environments and structures.
- 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_69f76ee987588190906506e759be5db3 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.