Triple
T13175972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO tactical data links |
E313099
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military communication system |
C11609
|
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: military communication system Context triple: [NATO tactical data links, instanceOf, military communication system]
-
A.
military communications organization
A military communications organization is a structured unit responsible for planning, managing, and operating secure, reliable information and communication systems that support command, control, and coordination of military forces.
-
B.
military system
chosen
A military system is an organized structure of personnel, equipment, doctrines, and processes designed to plan, conduct, and support defense and combat operations.
-
C.
military radar system
A military radar system is an integrated sensor platform that emits and receives electromagnetic signals to detect, track, and classify airborne, maritime, or ground targets for surveillance, targeting, and defense operations.
-
D.
global communication system
A global communication system is an interconnected network of technologies, protocols, and infrastructures that enables real-time exchange of information across the world regardless of geographic location.
-
E.
military bridge-layer system
A military bridge-layer system is an armored, mobile engineering vehicle designed to rapidly deploy and retrieve temporary bridges to enable troops and vehicles to cross obstacles in combat environments.
- 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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:14 p.m.