Triple
T31097902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dnipro Hydroelectric Station |
E792585
|
entity |
| Predicate | connectsBanksOf |
P197167
|
FINISHED |
| Object | Dnieper River at Zaporizhzhia |
—
|
NE NERFINISHED |
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 at Zaporizhzhia | Statement: [Dnipro Hydroelectric Station, connectsBanksOf, Dnieper River at Zaporizhzhia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsBanksOf Context triple: [Dnipro Hydroelectric Station, connectsBanksOf, Dnieper River at Zaporizhzhia]
-
A.
connectsBank
Indicates a relationship where one entity serves to link or provide access between another entity and a bank or banking service.
-
B.
linksBank
Indicates a relationship where one entity serves as or identifies the banking institution associated with another entity.
-
C.
banksHost
Indicates that a financial institution (bank) provides hosting or custodial services for another entity’s assets, accounts, or operations.
-
D.
numberOfBanks
Indicates the quantity or count of banks associated with a given entity or context.
-
E.
hasBankOn
Indicates that one entity is located on or alongside the bank (edge) of another entity, typically a river, lake, or similar 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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69fe7b1b3460819081172731b52ac15b |
completed | May 9, 2026, 12:08 a.m. |
Created at: April 29, 2026, 9:03 p.m.