Triple
T6951066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barry Docks |
E160924
|
entity |
| Predicate | primaryCargoCurrently |
P5941
|
FINISHED |
| Object | general cargo |
—
|
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: general cargo | Statement: [Barry Docks, primaryCargoCurrently, general cargo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCargoCurrently Context triple: [Barry Docks, primaryCargoCurrently, general cargo]
-
A.
mainCargo
chosen
Indicates that one entity serves as the primary or principal cargo carried or transported by another entity.
-
B.
primaryCargoDirection
Indicates the main directional flow or orientation in which the primary cargo is being transported or moved.
-
C.
primaryCargoOperator
Indicates that an entity serves as the main organization responsible for operating or managing the cargo-related activities of another entity.
-
D.
notableCargo
Indicates that an entity is known for carrying or having carried a particularly important, famous, or otherwise noteworthy cargo.
-
E.
cargoLoading
Indicates the action or process of placing cargo onto a vehicle, vessel, or other transport medium for shipment or movement.
- 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_69c68850419081909fb426b8f5a304c7 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dacca12481908942ba793a104cc3 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bf0a7c8190b5ed4aca22ba9b97 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:29 p.m.