Triple
T20314047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish Water |
E510332
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public water utility company |
C5072
|
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: public water utility company Context triple: [Scottish Water, instanceOf, public water utility company]
-
A.
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.
-
B.
public utility company
chosen
A public utility company is an organization, often government-regulated, that provides essential services such as electricity, water, gas, or telecommunications to the public, typically operating as a natural monopoly to ensure reliable and widespread access.
-
C.
utilities company
A utilities company is an organization that provides essential public services such as electricity, gas, water, or telecommunications to residential, commercial, and industrial customers, typically under government regulation.
-
D.
municipal water supply facility
A municipal water supply facility is an infrastructure complex that sources, treats, stores, and distributes potable water to meet the needs of a community or city.
-
E.
hydropower authority
A hydropower authority is an organization responsible for planning, regulating, developing, and managing hydropower resources and facilities within a specific jurisdiction.
- 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 11:19 a.m.