Triple
T27423311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N9 Warfare Systems |
E693106
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | warfare technology company |
C5343
|
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: warfare technology company Context triple: [N9 Warfare Systems, instanceOf, warfare technology company]
-
A.
defense company
chosen
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.
-
B.
defense industry holding company
A defense industry holding company is a corporate entity that owns and manages a portfolio of businesses involved in the research, development, production, and support of military and security-related products and services.
-
C.
defense industry leader
A defense industry leader is a high-level executive or organization that shapes strategic direction, drives innovation, and oversees the development and delivery of military and security solutions within the defense sector.
-
D.
armoured fighting vehicle manufacturer
An armoured fighting vehicle manufacturer is a company that designs, engineers, and produces military-grade, heavily protected combat vehicles such as tanks, infantry fighting vehicles, and armoured personnel carriers for armed forces and defense clients.
-
E.
military technology
Military technology encompasses the specialized tools, systems, and innovations developed and used by armed forces to enhance their capabilities in defense, offense, intelligence, and logistics.
- 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_69ef5208617081908f731d312e0fd1bc |
completed | April 27, 2026, 12:09 p.m. |
Created at: April 27, 2026, 12:36 p.m.