Triple
T5639032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birmingham gun trade |
E124219
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | arms manufacturing industry |
C14526
|
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: arms manufacturing industry Context triple: [Birmingham gun trade, instanceOf, arms manufacturing industry]
-
A.
arms manufacturer
An arms manufacturer is a company or entity that designs, produces, and supplies weapons, ammunition, and related military equipment for use by armed forces, security agencies, or private clients.
-
B.
defense industry
chosen
The defense industry comprises organizations and companies that research, develop, produce, and maintain military equipment, technologies, and services for national security and defense purposes.
-
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.
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 equipment
Military equipment comprises the specialized weapons, vehicles, protective gear, communication systems, and support tools designed, produced, and used by armed forces to conduct and support combat and defense operations.
- 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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
Created at: March 22, 2026, 3:41 p.m.