Triple
T37644962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MWSS Regulatory Office |
E936708
|
entity |
| Predicate | regulatesServiceType |
P118743
|
FINISHED |
| Object | urban water supply |
—
|
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: urban water supply | Statement: [MWSS Regulatory Office, regulatesServiceType, urban water supply]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatesServiceType Context triple: [MWSS Regulatory Office, regulatesServiceType, urban water supply]
-
A.
typeOfServiceRegulated
Indicates that a particular type of service is subject to regulation or oversight under a specified regulatory framework or authority.
-
B.
hasServiceType
Indicates that an entity is associated with or categorized by a particular type of service.
-
C.
overseesServiceType
chosen
Indicates that one entity has responsibility for supervising, managing, or directing the provision or operation of a particular type of service.
-
D.
regulatoryType
Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
-
E.
appliesToServiceType
Indicates that something is relevant or applicable specifically to a particular type or category of service.
- 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_69f76ed31d8881908405da6c6d2f0463 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe0d165a48819098b854318a50d76c |
completed | May 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69fe0931002481908a95b34f95e9f64e |
completed | May 8, 2026, 4:02 p.m. |
Created at: May 3, 2026, 4:18 p.m.