Triple
T23541889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holyoke Water Power Company gatehouses |
E577774
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | water control structures |
C5154
|
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: water control structures Context triple: [Holyoke Water Power Company gatehouses, instanceOf, water control structures]
-
A.
flood control facility
A flood control facility is an engineered structure or system designed to manage, divert, store, or reduce excess water flow to prevent or mitigate flooding in surrounding areas.
-
B.
water management structure
chosen
A water management structure is a constructed facility or system designed to control, store, convey, or regulate the quantity and movement of water in natural or built environments.
-
C.
lock and dam structure
A lock and dam structure is an engineered system on a waterway that combines a gated dam to control water levels with a lock chamber to raise and lower vessels between different elevations for safe and efficient navigation.
-
D.
water infrastructure
Water infrastructure encompasses the systems, facilities, and networks designed to source, treat, store, distribute, and manage water and wastewater for human, industrial, and environmental needs.
-
E.
levee system
A levee system is an integrated network of embankments, floodwalls, and related structures designed to contain or redirect water to protect land and infrastructure from flooding.
- 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_69e245f9d5d08190a4a20004e1784e20 |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 6:10 p.m.