Triple
T20968906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish iron industry |
E516443
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical industry sector |
C13859
|
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: historical industry sector Context triple: [Scottish iron industry, instanceOf, historical industry sector]
-
A.
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.
-
B.
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.
-
C.
economic sector
chosen
An economic sector is a broad category of economic activity that groups industries and businesses based on the type of goods or services they produce or the stage of production they represent.
-
D.
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.
-
E.
historic company
A historic company is an established business organization that has operated over a significant period of time and is notable for its enduring impact, legacy, or role in historical events or developments.
- 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_69e0b4fee5ac8190875fa9ceba1a5e5e |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 1:41 p.m.