Triple
T6596314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kishanganga Hydroelectric Plant |
E148483
|
entity |
| Predicate | peakLoadContribution |
P71963
|
FINISHED |
| Object | regional grid stabilization |
—
|
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: regional grid stabilization | Statement: [Kishanganga Hydroelectric Plant, peakLoadContribution, regional grid stabilization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakLoadContribution Context triple: [Kishanganga Hydroelectric Plant, peakLoadContribution, regional grid stabilization]
-
A.
peakUse
Indicates the time, condition, or context in which something reaches its maximum level of use or intensity.
-
B.
peakServicePeriod
Indicates the time interval during which a service experiences its highest or most intensive level of use or operation.
-
C.
peakRating
Indicates the highest rating value that has been achieved or recorded for an entity over a given period or context.
-
D.
peakDay
Indicates the specific day on which a quantity, activity, or effect reaches its maximum level within a given period.
-
E.
usagePeak
Indicates that the usage or consumption of something reaches its highest level or intensity during a particular time or condition.
- 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_69c687e7b8688190811ffee72e096468 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acfd17388190bd0bb8b2371e7df1 |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6cc988c0081909d22b86ca299331c |
completed | March 27, 2026, 6:29 p.m. |
Created at: March 27, 2026, 1:56 p.m.