Triple
T833978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bofors |
E18029
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Karlskoga |
E103430
|
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: Karlskoga | Statement: [Bofors, locatedIn, Karlskoga]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Karlskoga Context triple: [Bofors, locatedIn, Karlskoga]
-
A.
Trollhättan
Trollhättan is a city in western Sweden known for its historic role in the automotive industry and as the longtime home of Saab Automobile’s main production facilities.
-
B.
Östersund
Östersund is a city in central Sweden known for its strong winter sports tradition and repeated bids to host the Winter Olympics.
-
C.
Karlskoga, Sweden
chosen
Karlskoga, Sweden is an industrial town in central Sweden best known for its historic arms manufacturer Bofors and its association with Alfred Nobel.
-
D.
Jönköping
Jönköping is a city in southern Sweden, located at the southern end of Lake Vättern and known as a regional commercial and logistical hub.
-
E.
Strömstad
Strömstad is a coastal town and municipality in western Sweden, near the Norwegian border, known for its archipelago, tourism, and ferry connections.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a49389f44881909a608fb27d89f247 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abb84fe081909b8f4b4202845860 |
completed | March 1, 2026, 9:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a93395f2d8819082d622d1d6415073 |
completed | March 5, 2026, 7:41 a.m. |
Created at: March 1, 2026, 7:38 p.m.