Triple
T32750385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bofors Anti-Armour Division |
E837478
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defence industry unit |
C3644
|
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 industry unit Context triple: [Bofors Anti-Armour Division, instanceOf, defence industry unit]
-
A.
defence industry consortium
A defence industry consortium is a collaborative alliance of companies, research institutions, and sometimes government agencies that coordinate resources, expertise, and technologies to develop, produce, and support defense-related products and services.
-
B.
defense industry business unit
chosen
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.
-
C.
Ministry of Defence facility
A Ministry of Defence facility is a secured government-controlled site used for the planning, coordination, support, and execution of national defence and military operations.
-
D.
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.
-
E.
defense contractor business unit
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.
- 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_69f34937f97c8190b7f84bea045df3ae |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:12 a.m.