Triple
T3704390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saab Surveillance |
E80855
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defence technology company division |
C1872
|
CONCEPT FINISHED |
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: defence technology company division Context triple: [Saab Surveillance, instanceOf, defence technology company division]
-
A.
defense contractor division
A defense contractor division is an organizational unit within a defense company responsible for developing, producing, and supporting specific military or security-related products, services, or programs for government and allied clients.
-
B.
defense company
A defense company is an organization that designs, develops, manufactures, and supports military and security-related products, technologies, and services for governments and authorized entities.
-
C.
defense contractor business unit
chosen
A defense contractor business unit is an organizational division within a defense company that focuses on developing, producing, and supporting specific military or security-related products, services, or programs for government and allied customers.
-
D.
defense industry business unit
A defense industry business unit is an organizational division within a defense company that focuses on developing, producing, and supporting specific military or security-related products, services, or technologies for government and allied customers.
-
E.
engineering division
The engineering division is an organizational unit responsible for designing, developing, and maintaining technical systems, products, and infrastructure within a company or institution.
- F. None of above.
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_69ad8b1793888190a5f70e4b21dc05a1 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:33 p.m.