Triple
T28200852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopkinton public water supply system |
E716878
|
entity |
| Predicate | waterTreatmentProcess |
P54063
|
FINISHED |
| Object | filtration |
—
|
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: filtration | Statement: [Hopkinton public water supply system, waterTreatmentProcess, filtration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterTreatmentProcess Context triple: [Hopkinton public water supply system, waterTreatmentProcess, filtration]
-
A.
waterUsedForTreatmentOf
Indicates that water is utilized in the process of treating, managing, or remedying a specified condition, substance, or entity.
-
B.
usesWaterTreatment
chosen
Indicates that an entity applies or relies on a water treatment process or system in its operations or activities.
-
C.
waterTreatmentRecommended
Indicates that a specific water treatment process is advised or deemed necessary for the water in question.
-
D.
waterTreatedAt
Indicates that water has undergone treatment or purification at a specified facility or location.
-
E.
treatsWastewaterFor
Indicates that one entity processes and purifies wastewater on behalf of another entity or location.
- 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_69efd6b826908190857e6e7dad74ed93 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 27, 2026, 10:31 p.m.