Triple
T4644003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhakra Dam |
E101719
|
entity |
| Predicate | floodControlRole |
P42410
|
FINISHED |
| Object | regulates Sutlej River floods |
—
|
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: regulates Sutlej River floods | Statement: [Bhakra Dam, floodControlRole, regulates Sutlej River floods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floodControlRole Context triple: [Bhakra Dam, floodControlRole, regulates Sutlej River floods]
-
A.
providesFloodControlFor
chosen
Indicates that one entity offers protection or mitigation against flooding for another entity or area.
-
B.
hasFloodControlStructure
Indicates that an entity possesses or is equipped with a structure designed to manage, control, or mitigate flooding.
-
C.
hasFloodProtectionProject
Indicates that a flood protection project exists or is implemented for the referenced entity.
-
D.
riverControl
Indicates a relationship where one entity manages, regulates, or exerts authority over the flow, usage, or conditions of a river.
-
E.
floodGauge
Indicates that a device or measurement point is used to monitor and record the level or intensity of flooding at a specific location.
- 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_69bd43d3bc7c81908f81fcf380476b0f |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd6632708c8190b627d99363ab062c |
completed | March 20, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69bd620fc5e081908325ac8e6a6384ab |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:14 p.m.