Triple
T15130938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lockport Lock and Dam |
E361416
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | lock and dam complex |
C14228
|
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: lock and dam complex Context triple: [Lockport Lock and Dam, instanceOf, lock and dam complex]
-
A.
lock and dam structure
chosen
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.
-
B.
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.
-
C.
multipurpose dam
A multipurpose dam is a large engineered barrier built across a river or stream to store and regulate water for multiple uses such as irrigation, hydropower generation, flood control, water supply, and recreation.
-
D.
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.
-
E.
hydroelectric power complex
A hydroelectric power complex is an integrated facility that harnesses the energy of flowing or falling water—using dams, reservoirs, turbines, and generators—to produce and distribute electrical power.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:06 a.m.