Triple
T30918436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elbląg Canal inclined planes |
E787649
|
entity |
| Predicate | transportedEntity |
P91189
|
FINISHED |
| Object | boats |
—
|
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: boats | Statement: [Elbląg Canal inclined planes, transportedEntity, boats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportedEntity Context triple: [Elbląg Canal inclined planes, transportedEntity, boats]
-
A.
transportedWith
Indicates that one entity was moved or carried together with another entity as part of the same transport event.
-
B.
transportedIn
Indicates that one entity is carried or conveyed inside another entity as a means of transport.
-
C.
transportedFor
Indicates that one entity was moved or carried from one place to another for the benefit, use, or purpose of another entity or activity.
-
D.
transportedAfter
Indicates that one entity is transported only after the transportation of another entity has occurred in time.
-
E.
commonlyTransportedIn
chosen
Indicates that something is usually carried, moved, or conveyed using a particular vehicle, container, or mode of transport.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
Created at: April 29, 2026, 8:51 p.m.