Triple
T11500164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Narmada basin and Son–Ganga basin |
E272641
|
entity |
| Predicate | waterFlowSeparated |
P34484
|
FINISHED |
| Object | Narmada River waters |
—
|
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: Narmada River waters | Statement: [Narmada basin and Son–Ganga basin, waterFlowSeparated, Narmada River waters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterFlowSeparated Context triple: [Narmada basin and Son–Ganga basin, waterFlowSeparated, Narmada River waters]
-
A.
riverSeparatingFrom
Indicates that one river branches off or diverges from another river, creating a separation between their flow paths.
-
B.
separationInterface
Indicates a boundary or medium through which two distinct entities are separated or kept apart.
-
C.
watershedBetween
chosen
Indicates that a geographic feature or boundary serves as the dividing line between two drainage basins or river systems.
-
D.
waterFilled
Indicates that one entity is filled or occupied with water, typically to a certain level or capacity.
-
E.
hasFlowRegime
Indicates that one entity is characterized by, or operates under, a particular pattern or regime of flow.
- 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_69d6aae1b09881909ce2ded3fa0c14fa |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85de3e9c881909d6c55334f7a832d |
completed | April 10, 2026, 2:18 a.m. |
| PD | Predicate disambiguation | batch_69d808736c5c8190899b5b3b2e797f65 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.