Triple
T33005287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Budhi Gandaki River basin |
E844481
|
entity |
| Predicate | primaryWaterInputs |
P81004
|
FINISHED |
| Object | snowmelt |
—
|
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: snowmelt | Statement: [Budhi Gandaki River basin, primaryWaterInputs, snowmelt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryWaterInputs Context triple: [Budhi Gandaki River basin, primaryWaterInputs, snowmelt]
-
A.
primaryHydrology
Indicates the main hydrological feature (such as a river, lake, or water system) that predominantly characterizes or influences a given area or entity.
-
B.
sourceOfWaterSupply
Indicates that one entity serves as the origin or provider of another entity’s water supply.
-
C.
waterUse
Indicates the amount or manner in which water is consumed, utilized, or withdrawn by an entity or activity.
-
D.
primaryWaterways
Indicates that the related entities are connected through major or principal bodies of water, such as main rivers, canals, or shipping routes that serve as key waterways between them.
-
E.
waterInput
chosen
Indicates that an entity receives or is supplied with water from another source or system.
- 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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:23 a.m.