Triple
T16353282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polska Grupa Zbrojeniowa |
E397110
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defense holding company |
C24682
|
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: defense holding company Context triple: [Polska Grupa Zbrojeniowa, instanceOf, defense holding company]
-
A.
defense industry holding company
chosen
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.
-
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.
industrial holding company
An industrial holding company is a parent corporation that owns controlling interests in multiple industrial or manufacturing businesses, managing them strategically while typically leaving day-to-day operations to subsidiary management.
-
D.
publicly traded holding company
A publicly traded holding company is a corporation whose primary business is owning controlling interests in other companies, with its shares available for purchase on public stock exchanges.
-
E.
entertainment holding company
An entertainment holding company is a parent corporation that owns and manages controlling interests in multiple entertainment-related businesses, such as film studios, music labels, streaming platforms, and live event producers, to coordinate strategy and maximize overall value.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:07 a.m.