Triple
T18345015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scheibler industrial complex |
E439513
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic industrial district |
C27731
|
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 industrial district Context triple: [Scheibler industrial complex, instanceOf, historic industrial district]
-
A.
historic industrial area
chosen
A historic industrial area is a district characterized by preserved or repurposed factories, warehouses, and infrastructure that reflect the industrial heritage and economic history of a place.
-
B.
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.
-
C.
historic industrial structure
A historic industrial structure is a preserved building or facility originally designed for manufacturing, processing, or other industrial activities, valued today for its architectural, technological, and cultural significance.
-
D.
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.
-
E.
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.
- 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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:37 a.m.