Triple
T36632874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Level Commissioners |
E904374
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | statutory drainage authority |
C43457
|
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: statutory drainage authority Context triple: [Middle Level Commissioners, instanceOf, statutory drainage authority]
-
A.
drainage district
chosen
A drainage district is a special governmental or quasi-governmental entity created to manage, finance, and maintain systems that remove excess water from land to prevent flooding and improve land usability.
-
B.
statutory harbour authority
A statutory harbour authority is a legally established body empowered by specific legislation to manage, regulate, and develop a designated harbour or port area, including its navigation, safety, and related infrastructure.
-
C.
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.
-
D.
statutory traditional authority body
A statutory traditional authority body is a legally recognized institution that formalizes and regulates the roles, powers, and functions of traditional leaders within a state’s governance framework.
-
E.
watershed district
A watershed district is a geographically defined area governed by an organization responsible for managing water resources, drainage, and related environmental concerns within a specific river or drainage basin.
- 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:11 p.m.