Triple
T25852696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jal Jeevan Mission |
E651258
|
entity |
| Predicate | typeOfWaterSupply |
P39319
|
FINISHED |
| Object | piped water supply to households |
—
|
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: piped water supply to households | Statement: [Jal Jeevan Mission, typeOfWaterSupply, piped water supply to households]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfWaterSupply Context triple: [Jal Jeevan Mission, typeOfWaterSupply, piped water supply to households]
-
A.
sourceOfWaterSupply
Indicates that one entity serves as the origin or provider of another entity’s water supply.
-
B.
waterType
Indicates the specific kind or category of water associated with an entity (e.g., fresh, salt, brackish).
-
C.
waterSourceType
Indicates the kind or category of source from which water is obtained.
-
D.
waterServiceType
chosen
Indicates the specific kind or category of water service provided or associated with an entity.
-
E.
waterSupplyShare
Indicates the proportion of a total water supply that is allocated to or used by a particular entity.
- 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 22, 2026, 7:59 a.m.