Triple
T36234471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northumbrian Water |
E891340
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | wastewater services company |
C4509
|
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: wastewater services company Context triple: [Northumbrian Water, instanceOf, wastewater services company]
-
A.
wastewater treatment facility
A wastewater treatment facility is an engineered system that collects, treats, and purifies sewage and industrial effluent to remove contaminants before safely returning the water to the environment or reusing it.
-
B.
environmental services company
An environmental services company is an organization that provides specialized solutions to manage, protect, and restore natural resources and ecosystems through activities such as waste management, pollution control, remediation, and sustainability consulting.
-
C.
water management company
A water management company is an organization that plans, operates, and maintains systems for sourcing, treating, distributing, conserving, and monitoring water resources for communities, industries, or agriculture.
-
D.
water quality treatment facility
A water quality treatment facility is an engineered system that processes raw water through physical, chemical, and biological methods to remove contaminants and produce safe, clean water for human and environmental use.
-
E.
sewer utility
chosen
A sewer utility is an organization or system responsible for collecting, transporting, treating, and safely disposing of wastewater and sewage from homes, businesses, and industries.
- 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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.