Triple
T28624889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cushman Hydroelectric Project |
E724491
|
entity |
| Predicate | FERCProjectType |
P161567
|
FINISHED |
| Object | hydroelectric |
—
|
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: hydroelectric | Statement: [Cushman Hydroelectric Project, FERCProjectType, hydroelectric]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FERCProjectType Context triple: [Cushman Hydroelectric Project, FERCProjectType, hydroelectric]
-
A.
hydropowerProjectType
chosen
Indicates the specific category or type of a hydropower project associated with an entity.
-
B.
typeOfDamProject
Indicates that a given project is classified as a dam-related project (i.e., it is a project whose type is a dam project).
-
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.
isHydroelectricProjectOn
Indicates that a hydroelectric project is located on or situated along a specified water body or site.
-
E.
hasHydroelectricProject
Indicates that an entity is associated with, operates, or contains a hydroelectric power generation project.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:35 a.m.