Triple
T35701025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Headquarters 613th Air and Space Operations Center |
E1031582
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | air and space operations center |
C40083
|
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: air and space operations center Context triple: [Headquarters 613th Air and Space Operations Center, instanceOf, air and space operations center]
-
A.
Air and Space Operations Center
chosen
An Air and Space Operations Center is a command and control facility that plans, directs, coordinates, and monitors air and space operations to achieve assigned military objectives.
-
B.
Space Delta
Space Delta is a specialized organizational unit within a space force structure, responsible for executing a distinct mission area such as operations, intelligence, or support in the space domain.
-
C.
Air Force Sustainment Center (AFSC)
The Air Force Sustainment Center (AFSC) is a major U.S. Air Force organization responsible for providing depot maintenance, supply chain management, and sustainment support to ensure the readiness and availability of air and space weapon systems.
-
D.
space operations center
A space operations center is a specialized facility that monitors, controls, and coordinates spacecraft, satellites, and related space missions in real time.
-
E.
National Defense Management Center
The National Defense Management Center is a centralized command and control facility responsible for coordinating, monitoring, and directing a nation's military and defense operations at the strategic level.
- 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_69f76e0d393c8190b6303c64408736db |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.