Triple
T28645623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scharnebeck twin ship lift |
E725046
|
entity |
| Predicate | hasVerticalLiftHeight |
P171004
|
FINISHED |
| Object | 38 meters |
—
|
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: 38 meters | Statement: [Scharnebeck twin ship lift, hasVerticalLiftHeight, 38 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVerticalLiftHeight Context triple: [Scharnebeck twin ship lift, hasVerticalLiftHeight, 38 meters]
-
A.
hasLift
Indicates that one entity is equipped with, contains, or provides access to a lift (elevator).
-
B.
hasLiftType
Indicates the specific type or category of lift associated with an entity.
-
C.
verticalLiftSpanLength
Indicates the length of the span that moves vertically in a lifting structure or mechanism.
-
D.
hasRetractablePitch
Indicates that an entity (typically a stadium or venue) possesses a playing surface or pitch that can be mechanically extended or withdrawn as needed.
-
E.
hasLiftOrLaunchSystem
Indicates that an entity is equipped with, or associated with, a system used to lift, launch, or otherwise deploy another object or vehicle.
- 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_69f01d8423888190bd2f4e52605bf261 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6984bb55c8190862eb8796868d188 |
completed | May 3, 2026, 12:35 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f6978ec27c8190a488e1f9c2566d38 |
completed | May 3, 2026, 12:32 a.m. |
Created at: April 28, 2026, 4:47 a.m.