Triple
T1362984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Congo River |
E29137
|
entity |
| Predicate | hydropowerPotential |
P27462
|
FINISHED |
| Object | very high |
—
|
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: very high | Statement: [Congo River, hydropowerPotential, very high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hydropowerPotential Context triple: [Congo River, hydropowerPotential, very high]
-
A.
hasHydroelectricProject
Indicates that an entity is associated with, operates, or contains a hydroelectric power generation project.
-
B.
hasGeothermalPotential
Indicates that an entity possesses conditions suitable for generating or exploiting geothermal energy.
-
C.
hasHydrologicalFunction
Indicates that something performs a role or action related to the movement, storage, or regulation of water within a hydrological system.
-
D.
hydropowerImportance
Indicates the degree to which hydropower is considered significant or valuable within a given context, such as an energy system, region, or policy framework.
-
E.
drainageBasin
Indicates the area of land where all precipitation and surface water flow are collected and drained toward a particular river, lake, or other water body.
- 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_69a498d77abc8190913bf57e5f51d2c4 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c2b4ab3c8190ad692e32eee05976 |
completed | March 1, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69a4bef945c08190a027472fdd695ea5 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c06721488190ac7f6e012f21af3d |
completed | March 1, 2026, 10:40 p.m. |
Created at: March 1, 2026, 7:57 p.m.