Triple
T4793565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Wilmington |
E106658
|
entity |
| Predicate | managesCargoType |
P32692
|
FINISHED |
| Object | containerized 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: containerized cargo | Statement: [Port of Wilmington, managesCargoType, containerized cargo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesCargoType Context triple: [Port of Wilmington, managesCargoType, containerized cargo]
-
A.
mainCargo
Indicates that one entity serves as the primary or principal cargo carried or transported by another entity.
-
B.
hasCargoDivision
Indicates that an organization possesses a specific division or unit responsible for cargo-related operations or services.
-
C.
hasCargoRole
Indicates that an entity participates in a cargo-related capacity or function within a transport, shipment, or logistics context.
-
D.
hasCargoTrafficType
chosen
Indicates that an entity is associated with a specific type or category of cargo traffic it handles or supports.
-
E.
hasCargoServices
Indicates that an entity provides or is equipped to handle cargo transportation or freight services for another entity or location.
- 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_69bd43f591c881909e5a532388b0f3f3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd66072ebc8190ae0e6cef1e7b07e4 |
completed | March 20, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69bd622e1b408190806c15c61519fc74 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.