Triple
T15841728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kockums AB |
E384116
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | Saab Kockums |
E79643
|
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: Saab Kockums | Statement: [Kockums AB, successor, Saab Kockums]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Saab Kockums Context triple: [Kockums AB, successor, Saab Kockums]
-
A.
Saab Kockums
chosen
Saab Kockums is a Swedish shipyard and defense company best known for designing and building advanced submarines and naval vessels.
-
B.
Saab Automobile
Saab Automobile was a Swedish car manufacturer known for its innovative engineering, turbocharged engines, and distinctive, safety-focused designs.
-
C.
Saab AB
Saab AB is a Swedish aerospace and defense company known for developing military aircraft, advanced defense systems, and security solutions.
-
D.
Saab XWD
Saab XWD is Saab’s advanced all-wheel-drive system designed to enhance traction, handling, and stability in various driving conditions.
-
E.
Saab S 18A
The Saab S 18A was a Swedish reconnaissance and target-tug aircraft variant derived from the Saab 18 bomber platform.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e764088190afba6c5c1acf8199 |
completed | April 16, 2026, 8:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffc3b717c88190b974a44470136ff2 |
completed | May 9, 2026, 11:31 p.m. |
Created at: April 10, 2026, 4:50 a.m.