Triple
T31275758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Capstone Publication Spacepower |
E797510
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Space Force doctrine |
C39705
|
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: U.S. Space Force doctrine Context triple: [Space Capstone Publication Spacepower, instanceOf, U.S. Space Force doctrine]
-
A.
United States Space Force organizational system
The United States Space Force organizational system is the structured arrangement of commands, field units, roles, and processes designed to plan, conduct, and support space operations in alignment with national defense objectives.
-
B.
U.S. Space Force mission area
A U.S. Space Force mission area is a defined domain of responsibility that encompasses specific space-related operations, capabilities, and objectives required to support national security and joint military missions.
-
C.
United States Space Force delta
A United States Space Force delta is a military organizational unit, roughly equivalent to a wing, that is responsible for a specific mission area such as operations, training, or support within the Space Force.
-
D.
military doctrinal framework
chosen
A military doctrinal framework is a structured set of principles, concepts, and guidelines that shapes how armed forces plan, organize, and conduct operations across different levels of war.
-
E.
U.S. Army doctrine
U.S. Army doctrine is the authoritative, evolving body of fundamental principles, tactics, techniques, and procedures that guides how the Army organizes, trains, and conducts operations across the range of military activities.
- 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_69f224def9088190a37034eab3daf57f |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:13 p.m.