Triple

T27903538
Position Surface form Disambiguated ID Type / Status
Subject Jogulamba Gadwal district E705704 entity
Predicate hasHydelProject P15311 FINISHED
Object Priyadarshini Jurala 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: Priyadarshini Jurala hydroelectric project | Statement: [Jogulamba Gadwal district, hasHydelProject, Priyadarshini Jurala hydroelectric project]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHydelProject
Context triple: [Jogulamba Gadwal district, hasHydelProject, Priyadarshini Jurala hydroelectric project]
  • A. hasHydroelectricProject chosen
    Indicates that an entity is associated with, operates, or contains a hydroelectric power generation project.
  • B. isHydroelectricProjectOn
    Indicates that a hydroelectric project is located on or situated along a specified water body or site.
  • C. hasHydropowerRoleIn
    Indicates that an entity plays a specific role or function related to hydropower within the context of another entity, project, or activity.
  • D. isHydroelectricallyDeveloped
    Indicates that an entity has been developed to generate electricity using hydropower infrastructure or facilities.
  • E. hasHydroelectricInfrastructureNearby
    Indicates that there is hydroelectric infrastructure located in close proximity to the referenced entity.
  • 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_69ef96b490ac8190a412d04c5d009f3e completed April 27, 2026, 5:02 p.m.
NER Named-entity recognition batch_69f6562fd3488190be1acd8c526a28d2 completed May 2, 2026, 7:53 p.m.
PD Predicate disambiguation batch_69f651a931748190a637e631a52bbfaa completed May 2, 2026, 7:34 p.m.
Created at: April 27, 2026, 6:43 p.m.