Triple
T13536580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dom-Römer Quarter |
E323277
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | reconstructed historic district |
C33177
|
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: reconstructed historic district Context triple: [Dom-Römer Quarter, instanceOf, reconstructed historic district]
-
A.
historical district
A historical district is a geographically defined area recognized for its concentration of buildings, structures, and sites that collectively reflect significant cultural, architectural, or historical heritage.
-
B.
residential historic district
A residential historic district is a geographically defined neighborhood composed primarily of homes that collectively reflect significant historical, architectural, or cultural characteristics from a particular period or periods.
-
C.
revitalized historic building
A revitalized historic building is a preserved architectural structure that has been thoughtfully restored and modernized to serve contemporary functions while maintaining its original character and cultural significance.
-
D.
commercial historic district
A commercial historic district is a geographically defined area containing a concentration of historically significant commercial buildings and streetscapes that reflect the economic and cultural development of a community over time.
-
E.
historic district feature
A historic district feature is a physical element, structure, or landscape component within a designated historic area that contributes to its historical, architectural, or cultural significance.
- F. None of above. chosen
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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:45 p.m.