Triple
T1388944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Army Special Operations Aviation Command |
E29910
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special operations aviation command |
C6516
|
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: special operations aviation command Context triple: [U.S. Army Special Operations Aviation Command, instanceOf, special operations aviation command]
-
A.
aerial warfare service branch
An aerial warfare service branch is a military organization responsible for conducting and supporting combat and operational activities in the air and, increasingly, in space and cyberspace domains.
-
B.
naval air operation
A naval air operation is a coordinated military action involving aircraft launched from or supported by naval forces to achieve objectives at sea, in the air, or on land.
-
C.
reserve component of the United States Air Force
The reserve component of the United States Air Force is the part-time military force composed of Air Force Reserve and Air National Guard units that support and augment the active-duty Air Force during peacetime and wartime operations.
-
D.
fighter squadron
A fighter squadron is a military aviation unit composed of multiple fighter aircraft and their personnel, organized to conduct air-to-air and air-to-ground combat missions under a unified command.
-
E.
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.
- F. None of above. chosen
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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
Created at: March 1, 2026, 7:59 p.m.