Triple
T13990375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon Iron Company furnace |
E336555
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic iron furnace |
C8770
|
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 iron furnace Context triple: [Oregon Iron Company furnace, instanceOf, historic iron furnace]
-
A.
historic blast furnace complex
A historic blast furnace complex is an industrial site, often preserved as heritage, where iron ore was once smelted at high temperatures in large furnaces along with associated structures such as casting houses, coke ovens, and worker facilities.
-
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.
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.
-
D.
historic industrial structure
chosen
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.
-
E.
historic fire station
A historic fire station is a preserved or restored former firefighting facility that reflects the architectural style, equipment, and community role of fire services from a specific past era.
- 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_69d81c639e808190a0e4b4f3d31c6a59 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:18 p.m.