Triple
T37907686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South West Water |
E945598
|
entity |
| Predicate | hasTariffType |
P9385
|
FINISHED |
| Object | metered water charges |
—
|
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: metered water charges | Statement: [South West Water, hasTariffType, metered water charges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTariffType Context triple: [South West Water, hasTariffType, metered water charges]
-
A.
usesTariffSystem
Indicates that one entity applies or operates under a tariff-based system for pricing, taxation, or fees in its interactions or transactions.
-
B.
hasRateType
chosen
Indicates the specific category or scheme under which a rate (such as a price, fee, or interest) is defined or applied.
-
C.
tariffStructure
Indicates the specific schedule, rates, and rules that define how tariffs or fees are applied within a pricing or taxation system.
-
D.
hasTariffZoneSystem
Indicates that an entity uses or is governed by a defined tariff zone system for determining prices, fees, or charges.
-
E.
typeOfTariffPreference
Indicates the specific category or kind of tariff preference applied within a trade or customs context.
- 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_69f76ef20bb0819088b5b6ceecb0b8fc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:20 p.m.