Triple
T2015285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Ramsgate |
E43779
|
entity |
| Predicate | hasBerthDepth |
P34504
|
FINISHED |
| Object | suitable for small to medium-sized vessels |
—
|
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: suitable for small to medium-sized vessels | Statement: [Port of Ramsgate, hasBerthDepth, suitable for small to medium-sized vessels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBerthDepth Context triple: [Port of Ramsgate, hasBerthDepth, suitable for small to medium-sized vessels]
-
A.
hasBerths
Indicates that one entity provides or contains sleeping or docking berths for another entity.
-
B.
isDeepWaterPort
Indicates that a port has sufficiently deep water to accommodate large, heavily loaded vessels without grounding.
-
C.
maximumVesselDraft
Indicates the greatest depth a vessel can safely extend below the waterline, typically limiting where it can navigate or dock.
-
D.
riverbedDepth
Indicates the depth or vertical distance from the water surface to the bottom of a river at a given location or time.
-
E.
berthingOrDockingTarget
Indicates that an entity serves as the location or structure where a vessel or vehicle is intended to berth or dock.
- 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_69a88716e9f08190946313fdc949e3cf |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8cb16048190bc626685fbb5f707 |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a03a1c81909ad50d56667db2d5 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb83e7888819096dc40275c77daff |
completed | March 7, 2026, 5:31 a.m. |
Created at: March 4, 2026, 7:37 p.m.