Triple
T17606624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trench Broom |
E428848
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Thompson submachine gun variant |
C24042
|
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: Thompson submachine gun variant Context triple: [Trench Broom, instanceOf, Thompson submachine gun variant]
-
A.
recoilless rifle variant
A recoilless rifle variant is a modified form of a recoilless gun designed to launch projectiles with minimal recoil, typically through specialized venting or counter-mass systems, for use in portable or vehicle-mounted anti-armor or support roles.
-
B.
submachine gun family
chosen
A submachine gun family is a group of closely related submachine gun models that share a common design lineage, core operating mechanism, and often interchangeable parts, but differ in specific features such as caliber, size, or configuration.
-
C.
7.62 mm machine gun
A 7.62 mm machine gun is a belt- or magazine-fed automatic firearm chambered for 7.62 mm cartridges, designed to deliver sustained, high-rate fire for infantry support or vehicle-mounted roles.
-
D.
.380 ACP pistol
A .380 ACP pistol is a compact, semi-automatic handgun chambered for the .380 ACP cartridge, commonly used for concealed carry and personal defense due to its small size and manageable recoil.
-
E.
Browning machine gun family member
A Browning machine gun family member is a recoil- or gas-operated automatic firearm derived from John Browning’s designs, sharing common mechanical principles, layout, and often interchangeable components within the Browning lineage.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:51 a.m.