Triple
T29272206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Aalborg |
E742148
|
entity |
| Predicate | servesCargoType |
P96313
|
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 Aalborg, servesCargoType, containerized cargo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesCargoType Context triple: [Port of Aalborg, servesCargoType, containerized cargo]
-
A.
supportsCargoType
chosen
Indicates that one entity is capable of handling, transporting, or accommodating a specified type of cargo.
-
B.
hasCargoServices
Indicates that an entity provides or is equipped to handle cargo transportation or freight services for another entity or location.
-
C.
mainCargo
Indicates that one entity serves as the primary or principal cargo carried or transported by another entity.
-
D.
typeOfHaulage
Indicates the kind or category of haulage service or transport operation associated with an entity.
-
E.
commercialCargoProvider
Indicates that an entity serves as a provider of commercial cargo transport or delivery services for 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_69f0912124d48190a046642b69407f4c |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: April 28, 2026, 12:48 p.m.