Triple
T10173795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Narayanpur Dam |
E235797
|
entity |
| Predicate | hydroelectricPlantType |
P21222
|
FINISHED |
| Object | run-of-river |
—
|
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: run-of-river | Statement: [Narayanpur Dam, hydroelectricPlantType, run-of-river]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hydroelectricPlantType Context triple: [Narayanpur Dam, hydroelectricPlantType, run-of-river]
-
A.
powerplantType
chosen
Indicates the specific kind or category of power plant associated with an entity, based on how it generates energy.
-
B.
hydroelectricStationCapacity
Indicates the maximum amount of electrical power that a hydroelectric station is capable of producing under specified conditions.
-
C.
hydroelectricStationCommissioned
Indicates that a hydroelectric power station has been officially brought into operation or service on a specific date or in a specific context.
-
D.
powerplant
Indicates that an entity functions as a facility or installation where energy sources are converted into usable power, typically electricity.
-
E.
powerplantTypeTested
Indicates that a specific type of power plant has been subjected to testing or evaluation.
- 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_69ca84d1d5f88190ab878a1021ecff68 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdeca0dc508190916f2a1bbb288192 |
completed | April 2, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69cd7c79f21c8190a7f31b2eab80b8ba |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:11 p.m.