Triple
T29773814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colchester water supply system |
E755321
|
entity |
| Predicate | waterTypeSupplied |
P39319
|
FINISHED |
| Object | drinking water |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: drinking water | Statement: [Colchester water supply system, waterTypeSupplied, drinking water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterTypeSupplied Context triple: [Colchester water supply system, waterTypeSupplied, drinking water]
-
A.
waterType
Indicates the specific kind or category of water associated with an entity (e.g., fresh, salt, brackish).
-
B.
waterServiceType
chosen
Indicates the specific kind or category of water service provided or associated with an entity.
-
C.
waterSourceType
Indicates the kind or category of source from which water is obtained.
-
D.
sourceOfWaterSupply
Indicates that one entity serves as the origin or provider of another entity’s water supply.
-
E.
waterSourceSystem
Indicates a system that supplies, manages, or distributes water as a source for use by other entities.
- F. None of above.
Provenance (3 batches)
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_69f0ef878574819088c867fd1a5c8b86 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 28, 2026, 8:44 p.m.