Triple

T14259086
Position Surface form Disambiguated ID Type / Status
Subject Hyderabad water supply system E353462 entity
Predicate waterQualityStandard P649 FINISHED
Object drinking water standard 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 standard | Statement: [Hyderabad water supply system, waterQualityStandard, drinking water standard]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: waterQualityStandard
Context triple: [Hyderabad water supply system, waterQualityStandard, drinking water standard]
  • A. drinkingWaterStandard chosen
    Indicates that something meets an established quality or safety standard for drinking water.
  • B. hasWaterQualityDesignation
    Indicates that an entity has been assigned a specific official classification or status regarding its water quality.
  • C. waterQualityProtection
    Indicates efforts, measures, or responsibilities aimed at preserving or improving the cleanliness, safety, and ecological integrity of water resources.
  • D. waterQualityUse
    Indicates the way in which water quality is evaluated, classified, or applied for specific purposes or uses.
  • E. waterQualityIssues
    Indicates that there are problems or concerns with the condition, safety, or suitability of a water source.
  • 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_69d8278c43e08190824146f4632b89a5 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de6352611c819090d062fe3079cd03 completed April 14, 2026, 3:54 p.m.
PD Predicate disambiguation batch_69de2a7d586c8190846ff242bbf5ac53 completed April 14, 2026, 11:52 a.m.
Created at: April 10, 2026, 1:09 a.m.