Triple
T4072799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ERAWA |
E86686
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | explosive reactive armor system |
C6153
|
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: explosive reactive armor system Context triple: [ERAWA, instanceOf, explosive reactive armor system]
-
A.
composite armour
Composite armour is a protective material system made from multiple layers of different substances (such as ceramics, metals, and polymers) engineered to work together to better absorb, deflect, and dissipate the energy of incoming threats than a single homogeneous material.
-
B.
anti-armor missile
An anti-armor missile is a guided munition designed specifically to detect, track, and destroy armored targets such as tanks and armored vehicles using high-penetration warheads.
-
C.
ablative thermal protection system
An ablative thermal protection system is a heat shield that protects a spacecraft by sacrificially charring, melting, and eroding material to absorb and carry away extreme reentry heat.
-
D.
defensive avionics system
A defensive avionics system is an integrated suite of onboard sensors, processors, and countermeasure devices designed to detect, identify, and protect an aircraft from hostile threats such as radar, missiles, and electronic attacks.
-
E.
tank armour
chosen
Tank armour is the protective material and structural design applied to a tank’s hull and turret to resist and mitigate damage from enemy fire, explosives, and other battlefield threats.
- 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_69aed93ebe448190a1f1686e28740ac9 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:38 p.m.