Triple
T7639076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikiszowiec historic workers’ district |
E172953
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic workers’ district |
C15607
|
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: historic workers’ district Context triple: [Nikiszowiec historic workers’ district, instanceOf, historic workers’ district]
-
A.
historic industrial complex
A historic industrial complex is a large-scale, often multi-building site where past manufacturing, processing, or extractive activities took place, retaining significant architectural, technological, and cultural heritage value.
-
B.
historic market district
A historic market district is a preserved urban area where traditional marketplaces, architecture, and cultural practices converge to reflect the commercial and social life of a community across time.
-
C.
historic suburb
A historic suburb is a residential area on the outskirts of a city characterized by long-established neighborhoods, preserved architecture, and cultural or historical 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 subdistrict
chosen
A historic subdistrict is a geographically defined area within a larger district that contains a concentration of buildings, structures, or sites recognized for their historical, architectural, or cultural significance and is subject to preservation guidelines or protections.
- 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_69c69952849881908fdcea7a93bfc307 |
completed | March 27, 2026, 2:50 p.m. |
Created at: March 27, 2026, 3:57 p.m.