Triple
T2041328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liverpool2 container terminal |
E44750
|
entity |
| Predicate | berthType |
P35993
|
FINISHED |
| Object | deep-water berth |
—
|
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: deep-water berth | Statement: [Liverpool2 container terminal, berthType, deep-water berth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: berthType Context triple: [Liverpool2 container terminal, berthType, deep-water berth]
-
A.
hasBerths
Indicates that one entity provides or contains sleeping or docking berths for another entity.
-
B.
berthingSystem
Indicates a system or mechanism used to dock, moor, or secure one vehicle, vessel, or structure to another.
-
C.
harborType
Indicates the specific kind or classification of a harbor associated with an entity.
-
D.
berthingOrDockingTarget
Indicates that an entity serves as the location or structure where a vessel or vehicle is intended to berth or dock.
-
E.
determinedBerthIn
Indicates that an entity has been assigned or allocated to a specific berth or docking position.
- 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_69a889159ec481908f9e4472d9f480c7 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abbc2c3f6c8190aff07097b2654e52 |
completed | March 7, 2026, 5:48 a.m. |
| PD | Predicate disambiguation | batch_69abb7aa00d4819086d347d9a08f81a0 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abbc2b07d48190ba9d67353167b472 |
completed | March 7, 2026, 5:48 a.m. |
Created at: March 4, 2026, 7:39 p.m.