Triple
T31875815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Bristol |
E813737
|
entity |
| Predicate | mainBulkCargoTerminal |
P2420
|
FINISHED |
| Object | Avonmouth Docks |
—
|
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: Avonmouth Docks | Statement: [Port of Bristol, mainBulkCargoTerminal, Avonmouth Docks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainBulkCargoTerminal Context triple: [Port of Bristol, mainBulkCargoTerminal, Avonmouth Docks]
-
A.
hasCargoTerminal
chosen
Indicates that a location or facility includes or is equipped with a cargo terminal for handling freight.
-
B.
mainCargo
Indicates that one entity serves as the primary or principal cargo carried or transported by another entity.
-
C.
hasMainBulkCargoPort
Indicates that an entity serves as the primary port used for handling bulk cargo for another entity.
-
D.
servesAsCargoHubFor
Indicates that one entity functions as a central location or facility for handling, consolidating, and distributing cargo associated with another entity.
-
E.
hasContainerTerminal
Indicates that one entity possesses, includes, or is associated with a container terminal as part of its facilities or infrastructure.
- 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_69f6b0a50fcc8190b0b5ffc5f81daba9 |
completed | May 3, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:55 p.m.