Triple
T16792765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuri Chhu |
E408152
|
entity |
| Predicate | hydropowerPlantType |
P21222
|
FINISHED |
| Object | run-of-the-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-the-river | Statement: [Kuri Chhu, hydropowerPlantType, run-of-the-river]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hydropowerPlantType Context triple: [Kuri Chhu, hydropowerPlantType, run-of-the-river]
-
A.
powerplantType
chosen
Indicates the specific kind or category of power plant associated with an entity, based on how it generates energy.
-
B.
powerplantTypeTested
Indicates that a specific type of power plant has been subjected to testing or evaluation.
-
C.
rankAmongWorldHydroelectricPlantsByCapacity
Indicates the position of a hydroelectric plant in a global ranking ordered by its electricity generation capacity.
-
D.
hydroelectricStationCapacity
Indicates the maximum amount of electrical power that a hydroelectric station is capable of producing under specified conditions.
-
E.
powerplantRole
Indicates that one entity serves in a specific functional or operational role relative to a power plant.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2a7817c8190a53d0cfb5ef66a71 |
completed | April 18, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.