Triple
T4293222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Delta 3 |
E99645
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space electromagnetic warfare unit |
C409
|
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: space electromagnetic warfare unit Context triple: [Space Delta 3, instanceOf, space electromagnetic warfare unit]
-
A.
United States Space Force field command
A United States Space Force field command is a major organizational echelon responsible for executing a broad, mission-specific portfolio of space operations, support, or training functions under the direction of Space Operations Command.
-
B.
space wing
A space wing is a specialized aerospace unit or structural component designed for maneuvering, stabilizing, or housing systems on spacecraft operating in outer space or near-space environments.
-
C.
space component
A space component is a discrete, reusable element or module designed to perform a specific function within a larger space system or environment.
-
D.
space communication network
A space communication network is an interconnected system of ground stations, satellites, and relay nodes that enables the reliable transmission, routing, and reception of data across space and between space-based and terrestrial assets.
-
E.
military communications organization
chosen
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.
- 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_69b3455175088190aa79c6e03b86647e |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:08 p.m.