Triple
T13098238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krasnoyarsk Dam |
E310645
|
entity |
| Predicate | shipLiftType |
P1984
|
FINISHED |
| Object | inclined plane ship lift |
—
|
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: inclined plane ship lift | Statement: [Krasnoyarsk Dam, shipLiftType, inclined plane ship lift]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipLiftType Context triple: [Krasnoyarsk Dam, shipLiftType, inclined plane ship lift]
-
A.
hasLiftType
chosen
Indicates the specific type or category of lift associated with an entity.
-
B.
typeOfHaulage
Indicates the kind or category of haulage service or transport operation associated with an entity.
-
C.
hasLift
Indicates that one entity is equipped with, contains, or provides access to a lift (elevator).
-
D.
laterShipType
Indicates that one ship type chronologically succeeds or is introduced after another ship type.
-
E.
berthType
Indicates the specific kind or category of berth associated with an entity, such as the type of sleeping or docking space provided.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d981500d34819097037b3c3c33627b |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:04 p.m.