Triple
T22326899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strømmens Værksted |
E551923
|
entity |
| Predicate | acquiredBy |
P347
|
FINISHED |
| Object | Aker |
—
|
NE NERFINISHED |
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: Aker | Statement: [Strømmens Værksted, acquiredBy, Aker]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aker Context triple: [Strømmens Værksted, acquiredBy, Aker]
-
A.
Aker
Aker is a historical area and former municipality that once surrounded and included much of what is now Oslo, Norway.
-
B.
Aker Stord
chosen
Aker Stord is a Norwegian shipyard and offshore construction company located on the island of Stord, known for building and outfitting ships and oil and gas installations.
-
C.
Hanevik
Hanevik is a small village in western Norway located within Askøy Municipality in Vestland county.
-
D.
Aasen
Aasen is a Norwegian surname most famously borne by Ivar Aasen, the linguist who created the Nynorsk written standard of the Norwegian language.
-
E.
Namsen
Namsen is a major river in Trøndelag county, Norway, renowned for its salmon fishing and central role in the Namdalen region.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157693460819087c165481eb9e128 |
completed | April 29, 2026, 12:57 a.m. |
Created at: April 16, 2026, 8:42 p.m.