Triple
T31704354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EUROPAAMS |
E809139
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defence industry consortium |
C59592
|
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 consortium Context triple: [EUROPAAMS, instanceOf, defence industry consortium]
-
A.
defense industry joint venture
A defense industry joint venture is a collaborative business entity formed by two or more organizations to jointly develop, produce, or support military and security-related products or services, sharing resources, risks, and profits.
-
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 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.
-
D.
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.
-
E.
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.
- F. None of above. chosen
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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:13 p.m.