Triple
T11632065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Bellingham |
E276420
|
entity |
| Predicate | typeOfPortActivities |
P61144
|
FINISHED |
| Object | cargo handling |
—
|
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: cargo handling | Statement: [Port of Bellingham, typeOfPortActivities, cargo handling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPortActivities Context triple: [Port of Bellingham, typeOfPortActivities, cargo handling]
-
A.
portActivity
chosen
Indicates the level or type of operational activity occurring at a port, such as ship movements, cargo handling, or related maritime operations.
-
B.
typeOfPortFacility
Indicates that one port facility is classified as a specific type or category of port facility in relation to another.
-
C.
hasActivityType
Indicates the specific kind or category of activity associated with an entity or event.
-
D.
mannerOfActivity
Indicates the way or style in which an activity is performed or carried out.
-
E.
hasPortType
Indicates that an entity is associated with, or characterized by, a specific type or category of port.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a25aa9188190ab13d79139f37e7e |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.