Triple

T28621257
Position Surface form Disambiguated ID Type / Status
Subject Jammu municipal water supply system E724390 entity
Predicate waterQualityObjective P18606 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: [Jammu municipal water supply system, waterQualityObjective, potable water]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: waterQualityObjective
Context triple: [Jammu municipal water supply system, waterQualityObjective, potable water]
  • A. waterQualityProtection
    Indicates efforts, measures, or responsibilities aimed at preserving or improving the cleanliness, safety, and ecological integrity of water resources.
  • B. drinkingWaterStandard
    Indicates that something meets an established quality or safety standard for drinking water.
  • C. waterQualityUse chosen
    Indicates the way in which water quality is evaluated, classified, or applied for specific purposes or uses.
  • D. hasWaterQualityDesignation
    Indicates that an entity has been assigned a specific official classification or status regarding its water quality.
  • 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_69f01d822ac08190932de59ec2268ed2 completed April 28, 2026, 2:37 a.m.
NER Named-entity recognition batch_69f73223675481908c1bc3208c0f5284 completed May 3, 2026, 11:31 a.m.
PD Predicate disambiguation batch_69f7317690108190b3aae2cd2e1d069e completed May 3, 2026, 11:28 a.m.
Created at: April 28, 2026, 4:33 a.m.