Triple
T34528250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manjira Water Supply Scheme |
E886463
|
entity |
| Predicate | waterSourceReservoir |
P11309
|
FINISHED |
| Object | Singur reservoir |
—
|
NE NERFINISHED |
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: Singur reservoir | Statement: [Manjira Water Supply Scheme, waterSourceReservoir, Singur reservoir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterSourceReservoir Context triple: [Manjira Water Supply Scheme, waterSourceReservoir, Singur reservoir]
-
A.
reservoir
chosen
Indicates that one entity serves as a storage or containment source (often for a resource) that can supply or affect another entity.
-
B.
reservoirLocation
Indicates that a reservoir is geographically located at or within a specified place or region.
-
C.
reservoirAlsoKnownAs
Indicates that a reservoir is referred to by an alternative name or alias.
-
D.
reservoirType
Indicates the specific kind or classification of a reservoir associated with an entity.
-
E.
reservoirRiver
Indicates that a reservoir is supplied or drained by, and thus hydrologically connected to, a particular river.
- 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: May 1, 2026, 2:02 a.m.