Triple
T37839999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Raahe |
E943446
|
entity |
| Predicate | hasMainUser |
—
|
GENERATED |
| Object | SSAB Raahe steelworks |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainUser Context triple: [Port of Raahe, hasMainUser, SSAB Raahe steelworks]
-
A.
hasUser
Indicates that an entity is associated with or linked to a specific user.
-
B.
hasMainHost
Indicates that one entity serves as the primary or principal host for another entity.
-
C.
hasUsers
Indicates that an entity is associated with one or more users who use, own, or are linked to it.
-
D.
hasUserService
Indicates that an entity is associated with or utilizes a particular user-related service.
-
E.
hasSecondaryUser
Indicates that an entity is associated with an additional, non-primary user who also has access to or control over it.
- F. None of above. chosen
Provenance (1 batch)
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_69f76eeb0f7081908d6d3adbc469889c |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.