Triple
T27860805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krasnoyarsk hydroelectric power station |
E704221
|
entity |
| Predicate | hasShipLiftOrLock |
P51758
|
FINISHED |
| Object | ship lock |
—
|
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: ship lock | Statement: [Krasnoyarsk hydroelectric power station, hasShipLiftOrLock, ship lock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShipLiftOrLock Context triple: [Krasnoyarsk hydroelectric power station, hasShipLiftOrLock, ship lock]
-
A.
hasShipLock
chosen
Indicates that one entity possesses or is equipped with a ship lock used to control water levels for vessel passage.
-
B.
hasLockLift
Indicates that an entity is equipped with or features a mechanism that lifts or raises a lock.
-
C.
hasLift
Indicates that one entity is equipped with, contains, or provides access to a lift (elevator).
-
D.
hasLiftType
Indicates the specific type or category of lift associated with an entity.
-
E.
shipFlag
Indicates that a ship is registered under and legally operates under the authority of a specified national flag or registry.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 6:17 p.m.