Triple
T31875814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Bristol |
E813737
|
entity |
| Predicate | mainContainerTerminal |
P101593
|
FINISHED |
| Object | Royal Portbury Dock |
—
|
NE NERFINISHED |
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: Royal Portbury Dock | Statement: [Port of Bristol, mainContainerTerminal, Royal Portbury Dock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainContainerTerminal Context triple: [Port of Bristol, mainContainerTerminal, Royal Portbury Dock]
-
A.
hasContainerTerminal
chosen
Indicates that one entity possesses, includes, or is associated with a container terminal as part of its facilities or infrastructure.
-
B.
hasCargoTerminal
Indicates that a location or facility includes or is equipped with a cargo terminal for handling freight.
-
C.
hasContainerTerminalOperator
Indicates that an entity is operated or managed by a specific container terminal operator.
-
D.
ターミナル設備
Indicates a relationship where terminal facilities (such as stations, ports, or terminals) are provided, used, or involved as key infrastructure in a transportation or logistics context.
-
E.
terminalSide
Indicates that one entity is located at or forms the end boundary or terminal edge of another entity.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 30, 2026, 11:55 p.m.