Triple
T14017049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johannesburg drainage system |
E337230
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | stormwater management system |
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: stormwater management system Context triple: [Johannesburg drainage system, instanceOf, stormwater management system]
-
A.
stormwater management agency
A stormwater management agency is an organization responsible for planning, regulating, and maintaining systems and policies that control, treat, and safely convey stormwater to protect communities and the environment.
-
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.
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.
-
D.
water management project
A water management project is an organized initiative that plans, develops, and operates systems and practices to sustainably collect, store, distribute, and protect water resources for human and environmental needs.
-
E.
hydrological system
A hydrological system is the interconnected network of water storage and movement through the atmosphere, land, and water bodies, driven by processes such as precipitation, evaporation, infiltration, and runoff.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:19 p.m.