Triple

T35420372
Position Surface form Disambiguated ID Type / Status
Subject Gaganachukki Falls E1023766 entity
Predicate nearbyHydropowerFacility P144900 FINISHED
Object Shivanasamudra hydroelectric project NE NERFINISHED

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: Shivanasamudra hydroelectric project | Statement: [Gaganachukki Falls, nearbyHydropowerFacility, Shivanasamudra hydroelectric project]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: nearbyHydropowerFacility
Context triple: [Gaganachukki Falls, nearbyHydropowerFacility, Shivanasamudra hydroelectric project]
  • A. hasHydroelectricInfrastructureNearby chosen
    Indicates that there is hydroelectric infrastructure located in close proximity to the referenced entity.
  • B. hasHydropowerRoleIn
    Indicates that an entity plays a specific role or function related to hydropower within the context of another entity, project, or activity.
  • C. nearbyDownstreamDam
    Indicates that one dam is located a short distance downstream from another along the same watercourse.
  • D. hydropowerPotential
    Indicates the amount of energy that could be generated from water resources at a given site or region under specified conditions.
  • E. nearbyMajorDam
    Indicates that one entity is located close to a significant dam structure in its surrounding area.
  • 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_69f76df6704081909900c60be10d5849 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69feb5e66224819083b87c3707a5a5e0 completed May 9, 2026, 4:19 a.m.
PD Predicate disambiguation batch_69feb3bd700c8190991ed200cd3c04db completed May 9, 2026, 4:10 a.m.
Created at: May 3, 2026, 4:03 p.m.