Triple
T6439985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Historic Long Pond Ironworks |
E138192
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | industrial archaeological site |
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: industrial archaeological site Context triple: [Historic Long Pond Ironworks, instanceOf, industrial archaeological site]
-
A.
industrial site
An industrial site is a designated area of land developed and equipped with infrastructure and facilities for manufacturing, processing, storage, or other large-scale industrial operations.
-
B.
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.
-
C.
prehistoric mining site
A prehistoric mining site is an archaeological location where early human communities extracted raw materials such as stone, minerals, or metals using primitive tools and techniques before the advent of written records.
-
D.
historic mining complex
A historic mining complex is an integrated ensemble of former extraction, processing, and support facilities, structures, and landscapes that together illustrate the technological, economic, and social history of past mining activities.
-
E.
reconstructed historic site
A reconstructed historic site is a place where buildings, structures, or environments from the past have been rebuilt or significantly restored to approximate their original appearance and context for educational, commemorative, or touristic purposes.
- 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:45 p.m.