Triple
T1104950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saugus Iron Works National Historic Site |
E25467
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic industrial site |
C1959
|
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 site Context triple: [Saugus Iron Works National Historic Site, instanceOf, historic industrial site]
-
A.
historic blast furnace complex
chosen
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.
former industrial plant
A former industrial plant is a decommissioned facility that once housed large-scale manufacturing or processing operations, often leaving behind substantial physical infrastructure and potential environmental impacts.
-
C.
historic mining region
A historic mining region is an area where past extraction of minerals or ores significantly shaped its landscape, economy, culture, and built heritage, often leaving behind distinctive industrial sites and communities.
-
D.
historic park
A historic park is a preserved outdoor area that combines natural landscapes with sites, structures, and artifacts of historical significance for public education and recreation.
-
E.
historic monument
A historic monument is a significant structure, site, or object preserved for its cultural, architectural, or historical importance, symbolizing and commemorating events, people, or eras of the past.
- 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
Created at: March 1, 2026, 7:43 p.m.