Triple
T31097952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dnipro Dam |
E792586
|
entity |
| Predicate | affectsNavigation |
P178830
|
FINISHED |
| Object | Dnieper River navigation |
—
|
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: Dnieper River navigation | Statement: [Dnipro Dam, affectsNavigation, Dnieper River navigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectsNavigation Context triple: [Dnipro Dam, affectsNavigation, Dnieper River navigation]
-
A.
hasNavigationUse
Indicates that something is used for navigation or serves a navigational function in relation to another entity.
-
B.
enablesNavigationBetween
Indicates that one entity provides the means or capability for moving or transitioning between two other entities or locations.
-
C.
navigationEffect
Indicates the effect or outcome that a navigation action (such as moving between views, pages, or states) has on the system or user experience.
-
D.
hasNavigationPurpose
Indicates that something exists or is designed specifically to serve a navigational function or goal.
-
E.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
- 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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71421e8d08190807ccfb15d0f0ddb |
completed | May 3, 2026, 9:23 a.m. |
Created at: April 29, 2026, 9:03 p.m.