Triple
T25040434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murray River lock and weir system |
E627091
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hydraulic engineering infrastructure |
C26460
|
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: hydraulic engineering infrastructure Context triple: [Murray River lock and weir system, instanceOf, hydraulic engineering infrastructure]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
era of hydraulic engineering
The era of hydraulic engineering is a historical period characterized by the systematic design, construction, and management of water control structures and systems to support human activities such as agriculture, urbanization, transportation, and energy production.
-
E.
engineered waterway
chosen
An engineered waterway is a human-made or heavily modified channel or system designed to control, convey, or manage water for purposes such as navigation, irrigation, drainage, flood control, or power generation.
- 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_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:08 a.m.