Triple
T3703956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Air Forces Northern |
E80846
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | air component command |
C10545
|
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 component command Context triple: [U.S. Air Forces Northern, instanceOf, air component command]
-
A.
naval component command
A naval component command is a subordinate joint force command responsible for planning, directing, and coordinating naval operations within a designated theater or area of responsibility.
-
B.
service component command
A service component command is an encapsulated operation or request that a service component can execute, typically representing a discrete, reusable unit of business or technical functionality within a system.
-
C.
acquisition command
An acquisition command is an instruction or directive that initiates and controls the process of obtaining data, resources, or assets from a specified source.
-
D.
regional air command
chosen
A regional air command is a military organizational unit responsible for planning, directing, and controlling air operations within a specific geographic area.
-
E.
space operations command
A space operations command is a military or governmental organizational unit responsible for planning, directing, and controlling space-based assets and activities to support national security, communications, navigation, and situational awareness.
- 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_69ad8b1793888190a5f70e4b21dc05a1 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:33 p.m.