Triple
T37839999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Raahe |
E943446
|
entity |
| Predicate | hasMainUser |
P204417
|
FINISHED |
| Object | SSAB Raahe steelworks |
E1073665
|
NE 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: SSAB Raahe steelworks | Statement: [Port of Raahe, hasMainUser, SSAB Raahe steelworks]
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 (5 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_69f76eeb0f7081908d6d3adbc469889c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40fb8a7f1081908705b7d1507bb05e |
completed | June 28, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:19 p.m.