Triple
T31097886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dnipro Hydroelectric Station |
E792585
|
entity |
| Predicate | additionalFunction |
P2114
|
FINISHED |
| Object | navigation improvement |
—
|
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: navigation improvement | Statement: [Dnipro Hydroelectric Station, additionalFunction, navigation improvement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: additionalFunction Context triple: [Dnipro Hydroelectric Station, additionalFunction, navigation improvement]
-
A.
secondaryFunction
chosen
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
-
B.
actualFunction
Indicates that something serves as the real, operative function or role performed in practice, as opposed to a nominal or theoretical one.
-
C.
publicFunction
Indicates that a function or method is accessible from outside its defining scope, module, or class (i.e., it has public visibility).
-
D.
associatedFunction
Indicates that one entity has a related or linked function that is conceptually or operationally connected to it.
-
E.
additionalVow
Indicates that an entity makes or is associated with an extra or supplementary vow beyond an initial or primary vow.
- 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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:03 p.m.