Triple
T4644002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhakra Dam |
E101719
|
entity |
| Predicate | energyContribution |
P58869
|
FINISHED |
| Object | supplies power to northern grid of India |
—
|
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: supplies power to northern grid of India | Statement: [Bhakra Dam, energyContribution, supplies power to northern grid of India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyContribution Context triple: [Bhakra Dam, energyContribution, supplies power to northern grid of India]
-
A.
outputEnergy
Indicates that an entity produces or releases a certain amount or form of energy as a result of its operation or behavior.
-
B.
energyUse
Indicates the amount or rate at which an entity consumes energy to perform its functions or activities.
-
C.
energyRegime
Indicates the specific range or mode of energy conditions under which a process, interaction, or system operates or is characterized.
-
D.
energyUtilization
Indicates how effectively an entity uses available energy to perform work or sustain its functions.
-
E.
energyType
Indicates the kind or category of energy associated with an entity or process.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69bd663092cc81909308f89ee1a417e4 |
completed | March 20, 2026, 3:22 p.m. |
Created at: March 20, 2026, 1:14 p.m.