Triple
T13175923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO Allied Air Command |
E313098
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | air and space 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 and space component command Context triple: [NATO Allied Air Command, instanceOf, air and space component command]
-
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.
air force commander
An air force commander is a senior military officer responsible for planning, directing, and overseeing air operations, personnel, and resources to achieve strategic and tactical objectives.
-
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.
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.
Air Force organization
An Air Force organization is a structured unit within an air force responsible for planning, directing, and executing air and space operations, support, or administration to achieve military objectives.
- 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.