Triple
T3134156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amsterdam–Rhine Canal |
E65486
|
entity |
| Predicate | maxVesselDraught |
P29240
|
FINISHED |
| Object | approximately 4 metres |
—
|
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: approximately 4 metres | Statement: [Amsterdam–Rhine Canal, maxVesselDraught, approximately 4 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxVesselDraught Context triple: [Amsterdam–Rhine Canal, maxVesselDraught, approximately 4 metres]
-
A.
maximumVesselDraft
chosen
Indicates the greatest depth a vessel can safely extend below the waterline, typically limiting where it can navigate or dock.
-
B.
maximumVesselAirDraft
Indicates the greatest vertical distance from the waterline to the highest point of a vessel that is allowed or applicable in a given context.
-
C.
hasBerthDepth
Indicates the depth of water available at a specific berth where a vessel can be moored.
-
D.
maximumShipBeam
Indicates the greatest allowable or observed width of a ship across its widest point.
-
E.
maximumVesselLength
Indicates the greatest allowable or observed length of a vessel in a given context or constraint.
- 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_69ad8581c25c8190b0d85ba9b9baa531 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada562540081908627950dd0b56a1e |
completed | March 8, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69ad9df840088190a26a1516f4c1f056 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.