Triple
T26367768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Vlaamse Waterweg nv |
E660388
|
entity |
| Predicate | typeOfTransportSupported |
P1379
|
FINISHED |
| Object | inland shipping |
—
|
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: inland shipping | Statement: [De Vlaamse Waterweg nv, typeOfTransportSupported, inland shipping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfTransportSupported Context triple: [De Vlaamse Waterweg nv, typeOfTransportSupported, inland shipping]
-
A.
transportType
chosen
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
B.
supportsMobilityType
Indicates that one entity provides compatibility with, or can function using, a specified type of mobility or movement mode.
-
C.
transportModePresent
Indicates that a particular mode of transportation is involved or available in the described context or event.
-
D.
isTransportationType
Indicates that one entity functions as a mode or category of transportation for the other entity.
-
E.
appliesToTransportMode
Indicates that a rule, condition, or characteristic is specifically associated with and relevant to a particular 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_69ee8126d52c8190bc0b34337c2c9aa8 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: April 26, 2026, 10:56 p.m.