Triple
T24759081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niederfinow Boat Lift |
E619377
|
entity |
| Predicate | transitTimeIncludingLocking |
P103916
|
FINISHED |
| Object | about 20 minutes |
—
|
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: about 20 minutes | Statement: [Niederfinow Boat Lift, transitTimeIncludingLocking, about 20 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transitTimeIncludingLocking Context triple: [Niederfinow Boat Lift, transitTimeIncludingLocking, about 20 minutes]
-
A.
liftTime
Indicates the duration or specific time period during which a lifting action or lift-related process occurs.
-
B.
timeToComplete
Indicates the duration required for an entity or process to be fully completed.
-
C.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
D.
peakDeliveryTime
Indicates the time period during which deliveries are expected to be at their highest volume or frequency.
-
E.
timeToTravelEndToEnd
chosen
Indicates the duration required to traverse from the starting point to the ending point of something (e.g., a route, path, or system) without interruption.
- 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 4:27 a.m.