Triple
T21123759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manned Orbiting Laboratory |
E520497
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Air Force space program |
C18113
|
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. Air Force space program Context triple: [Manned Orbiting Laboratory, instanceOf, U.S. Air Force space program]
-
A.
United States Air Force project
chosen
A United States Air Force project is an organized, time-bound initiative undertaken by the USAF to research, develop, test, or implement capabilities, systems, or operations in support of its strategic and tactical missions.
-
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.
space control squadron
A space control squadron is a military unit responsible for monitoring, protecting, and managing the use of space-based assets and the space domain to ensure operational advantage.
-
D.
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.
-
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.
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_69e0b50a623881909c0bbaf4f2c055e7 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:55 p.m.