Triple
T7050058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Vietnamese air defenses |
E163741
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | integrated air defense system |
C698
|
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: integrated air defense system Context triple: [North Vietnamese air defenses, instanceOf, integrated air defense system]
-
A.
integrated air defence system
chosen
An integrated air defence system is a coordinated network of sensors, command and control elements, and weapon systems designed to detect, track, and engage aerial threats to protect designated airspace and assets.
-
B.
ground-based air defense system
A ground-based air defense system is a coordinated set of land-deployed sensors, command-and-control elements, and weapon platforms designed to detect, track, and engage airborne threats such as aircraft, missiles, and drones.
-
C.
air and missile defense interceptor
An air and missile defense interceptor is a guided weapon system designed to detect, track, and destroy incoming aircraft, cruise missiles, or ballistic missiles before they reach their targets.
-
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.
self-propelled surface-to-air missile system
A self-propelled surface-to-air missile system is a mobile, ground-based weapons platform that integrates its own propulsion, radar, and missile launch capabilities to detect, track, and engage airborne targets.
- 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_69c6885f598c8190b6b6495c59d8d962 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:37 p.m.