Triple
T8139312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lechwehr (Lech weir at Landsberg) |
E190050
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | river engineering structure |
C19869
|
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: river engineering structure Context triple: [Lechwehr (Lech weir at Landsberg), instanceOf, river engineering structure]
-
A.
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.
-
B.
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.
-
C.
engineering structure
chosen
An engineering structure is a designed and constructed system of connected components that safely resists and transmits loads to fulfill a specific functional purpose in the built environment.
-
D.
concrete dam
A concrete dam is a massive engineered barrier constructed primarily from concrete to hold back and control the flow of water in a river or reservoir.
-
E.
canal infrastructure
Canal infrastructure encompasses the engineered systems, structures, and facilities—such as channels, locks, dams, embankments, and control mechanisms—designed to manage and support waterborne transport, irrigation, drainage, and water regulation along artificial waterways.
- 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_69ca82bd9900819099477cdc2eb4244f |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:35 p.m.