Triple
T22061887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JWICS |
E545173
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. military communications system |
C18787
|
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: U.S. military communications system Context triple: [JWICS, instanceOf, U.S. military communications system]
-
A.
U.S. Department of Defense network
chosen
A U.S. Department of Defense network is a secure, government-operated information and communications infrastructure used to support military operations, intelligence, logistics, and administrative functions across classified and unclassified environments.
-
B.
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.
-
C.
military base network
A military base network is an interconnected system of communication, data, and operational infrastructure linking facilities, units, and resources across one or more military installations to support command, control, logistics, and security functions.
-
D.
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.
-
E.
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.
- 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_69e11e3377c48190890c17407b9527d6 |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:27 p.m.