Triple
T14477316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dnieper Rapids |
E359005
|
entity |
| Predicate | engineeringImpact |
P54339
|
FINISHED |
| Object | improvement of continuous navigation on the Dnieper |
—
|
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: improvement of continuous navigation on the Dnieper | Statement: [Dnieper Rapids, engineeringImpact, improvement of continuous navigation on the Dnieper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineeringImpact Context triple: [Dnieper Rapids, engineeringImpact, improvement of continuous navigation on the Dnieper]
-
A.
infrastructureImpact
chosen
Indicates the effect that an action, event, or entity has on the condition, performance, or availability of infrastructure systems.
-
B.
encodingImpact
Indicates how one encoding or encoding choice affects, modifies, or constrains another process, representation, or outcome.
-
C.
impactDescription
Indicates a description of the effect, consequence, or influence that one entity, action, or event has on another.
-
D.
engineeringEmphasis
Indicates that something places a primary focus or specialization on engineering principles, methods, or activities.
-
E.
impactBuilding
Indicates that one entity physically collides with or strikes a building, causing an impact event.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9248edb48190a74eb032aeaac027 |
completed | April 14, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.