Triple
T36414646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Mills |
E896972
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic tidal mill complex |
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 tidal mill complex Context triple: [Three Mills, instanceOf, historic tidal mill complex]
-
A.
historic watchtower complex
A historic watchtower complex is a group of strategically positioned, often interconnected towers and supporting structures originally built for surveillance, communication, and defense across a landscape.
-
B.
historic gristmill
A historic gristmill is a traditional milling facility, often water- or wind-powered, where grain was ground into flour and which now serves as a preserved example of early industrial and agricultural technology.
-
C.
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.
-
D.
historic mill town
A historic mill town is a community that developed around water- or steam-powered mills, where industrial buildings, worker housing, and civic structures reflect the town’s past as a center of manufacturing and economic activity.
-
E.
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.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.