Triple
T29132928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chipping Norton textile industry |
E738427
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic local industry |
C10647
|
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 local industry Context triple: [Chipping Norton textile industry, instanceOf, historic local industry]
-
A.
historic industrial area
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 company town
A historic company town is a planned community built and owned by a single business or industry, where housing, services, and daily life were organized around and dependent on that employer’s operations.
-
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 industrial complex
chosen
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.
-
E.
historic industrial display
A historic industrial display is an exhibit that presents artifacts, machinery, and interpretive materials from past industrial activities to illustrate historical manufacturing processes, technologies, and their social impact.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 28, 2026, 11:32 a.m.