Triple
T20769958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crooked Falls |
E511200
|
entity |
| Predicate | isHydroelectricallyDeveloped |
P141449
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Crooked Falls, isHydroelectricallyDeveloped, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHydroelectricallyDeveloped Context triple: [Crooked Falls, isHydroelectricallyDeveloped, false]
-
A.
hasHydroelectricDevelopments
Indicates that one entity possesses, contains, or is associated with hydroelectric power generation installations or projects.
-
B.
hasHydroelectricProject
Indicates that an entity is associated with, operates, or contains a hydroelectric power generation 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.
hasHydroelectricHeritage
Indicates that an entity possesses historical or cultural significance related to hydroelectric power development, use, or infrastructure.
- F. None of above. chosen
Provenance (4 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_69e0b4ca01148190ac018e57e0cab46f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c265f7dc8190a084e35d38d2783a |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:36 p.m.