Triple
T2013797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USSF-67 |
E43747
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Space Force mission |
C5823
|
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 mission Context triple: [USSF-67, instanceOf, U.S. Space Force mission]
-
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.
NASA space mission
A NASA space mission is a coordinated, goal-driven endeavor planned and executed by NASA to explore, observe, or utilize space using specialized spacecraft, instruments, and supporting ground operations.
-
C.
SpaceX mission
A SpaceX mission is a coordinated aerospace operation conducted by SpaceX to transport payloads or crew to specific destinations in space, such as Earth orbit, the International Space Station, or beyond.
-
D.
NASA mission component
A NASA mission component is a distinct hardware, software, or operational element designed to perform a specific function that contributes to the overall objectives and success of a NASA space mission.
-
E.
military mission
chosen
A military mission is a coordinated operation undertaken by armed forces to achieve specific strategic, operational, or tactical objectives within defined constraints and rules of engagement.
- 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_69a88716e9f08190946313fdc949e3cf |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:37 p.m.