Triple
T38498975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roha |
E919774
|
entity |
| Predicate | riverUsage |
P121141
|
FINISHED |
| Object | source of water for industries |
—
|
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: source of water for industries | Statement: [Roha, riverUsage, source of water for industries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverUsage Context triple: [Roha, riverUsage, source of water for industries]
-
A.
waterUse
Indicates the amount or manner in which water is consumed, utilized, or withdrawn by an entity or activity.
-
B.
hasRiverUse
chosen
Indicates that one entity makes use of a river associated with another entity, such as for transport, irrigation, recreation, or other purposes.
-
C.
basinUse
Indicates that a basin is used for a particular purpose, activity, or function.
-
D.
usedWaterway
Indicates that one entity traveled, transported goods, or otherwise moved via a particular waterway as the route or medium of use.
-
E.
reservoirUse
Indicates the way a reservoir is utilized or the purpose for which its stored water is used.
- 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_69f76e9ddd4481908f8c04439d848f9d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:31 p.m.