Triple
T2119456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greenock Ocean Terminal |
E43883
|
entity |
| Predicate | hasCargoType |
P32692
|
FINISHED |
| Object | containers |
—
|
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: containers | Statement: [Greenock Ocean Terminal, hasCargoType, containers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCargoType Context triple: [Greenock Ocean Terminal, hasCargoType, containers]
-
A.
hasCargoAirline
Indicates that one entity operates as a cargo airline for, or provides cargo air transport services to, another entity.
-
B.
hasCargoTrafficType
chosen
Indicates that an entity is associated with a specific type or category of cargo traffic it handles or supports.
-
C.
hasCargoServices
Indicates that an entity provides or is equipped to handle cargo transportation or freight services for another entity or location.
-
D.
hasCargoDivision
Indicates that an organization possesses a specific division or unit responsible for cargo-related operations or services.
-
E.
mainCargo
Indicates that one entity serves as the primary or principal cargo carried or transported by 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_69a88717cfe48190b7ecdd68c824848a |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb32efb48190bcb99f30787a3a55 |
completed | March 7, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69abb7bbf9d881909d223b0cab7cab18 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.