Triple
T10902749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Sarnia |
E257486
|
entity |
| Predicate | supportsCargoType |
P96313
|
FINISHED |
| Object | petroleum products |
—
|
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: petroleum products | Statement: [Port of Sarnia, supportsCargoType, petroleum products]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCargoType Context triple: [Port of Sarnia, supportsCargoType, petroleum products]
-
A.
hasCargoServices
Indicates that an entity provides or is equipped to handle cargo transportation or freight services for another entity or location.
-
B.
cargoCapacityFeature
Indicates that an entity has a feature specifying how much cargo it can carry or accommodate.
-
C.
hasCargoAirline
Indicates that one entity operates as a cargo airline for, or provides cargo air transport services to, another entity.
-
D.
hasCargoRole
Indicates that an entity participates in a cargo-related capacity or function within a transport, shipment, or logistics context.
-
E.
cargoAccess
Indicates that an entity has permission or capability to access, enter, or interact with a cargo area or cargo-related contents.
- F. None of above. chosen
Provenance (4 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d761a4e9d48190b107839761a2152b |
completed | April 9, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_69d70d3d69e08190bb369e9a7927142c |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101de31c819090707635f6790559 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:22 p.m.