Triple
T32151029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cuban system of popular defense |
E821158
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | civil-military defense system |
C18880
|
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: civil-military defense system Context triple: [Cuban system of popular defense, instanceOf, civil-military defense system]
-
A.
military system
A military system is an organized structure of personnel, equipment, doctrines, and processes designed to plan, conduct, and support defense and combat operations.
-
B.
missile defense command and control system
A missile defense command and control system is an integrated network of sensors, communication links, decision-support tools, and engagement controls that detects, tracks, evaluates, and coordinates responses to missile threats in real time.
-
C.
military engineering system
A military engineering system is an integrated framework of technologies, processes, and organizational structures designed to plan, construct, maintain, and protect military infrastructure and capabilities in support of defense operations.
-
D.
naval defense system
A naval defense system is an integrated network of sensors, weapons, platforms, and command-and-control components designed to detect, deter, and neutralize maritime threats to ships, fleets, and coastal assets.
-
E.
civil-military coordination structure
chosen
A civil-military coordination structure is an organized framework that defines roles, processes, and communication channels between civilian authorities and military forces to plan, manage, and execute joint operations effectively and lawfully.
- 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_69f3490520d081909b2f1271dab75faa |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:31 a.m.