Triple
T37982320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magathane Water Treatment Plant |
E947586
|
entity |
| Predicate | typeOfWaterTreated |
P851
|
FINISHED |
| Object | potable 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: potable water | Statement: [Magathane Water Treatment Plant, typeOfWaterTreated, potable water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfWaterTreated Context triple: [Magathane Water Treatment Plant, typeOfWaterTreated, potable water]
-
A.
waterUsedForTreatmentOf
Indicates that water is utilized in the process of treating, managing, or remedying a specified condition, substance, or entity.
-
B.
waterTreatedAt
Indicates that water has undergone treatment or purification at a specified facility or location.
-
C.
typeOfWaterManaged
Indicates the specific kind or category of water that is overseen, controlled, or handled within a management context.
-
D.
usesWaterTreatment
Indicates that an entity applies or relies on a water treatment process or system in its operations or activities.
-
E.
waterType
chosen
Indicates the specific kind or category of water associated with an entity (e.g., fresh, salt, brackish).
- 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_69f76ef8a1d08190a741bbbc5970e3b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.