Triple
T14259069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyderabad water supply system |
E353462
|
entity |
| Predicate | usesGroundwater |
P11699
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hyderabad water supply system, usesGroundwater, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGroundwater Context triple: [Hyderabad water supply system, usesGroundwater, true]
-
A.
hasAquifer
Indicates that one entity possesses, contains, or overlies an aquifer associated with it.
-
B.
hasWaterUse
Indicates a relationship where one entity utilizes or consumes water for a particular purpose, process, or function.
-
C.
hasWatershedUse
Indicates that a particular type of use, activity, or function is associated with or applied to a watershed.
-
D.
usesWaterTreatment
Indicates that an entity applies or relies on a water treatment process or system in its operations or activities.
-
E.
waterSourceType
chosen
Indicates the kind or category of source from which water is obtained.
- 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.