Triple
T36482729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz program (space station operations phase) |
E898860
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | spacecraft operations phase |
C14566
|
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: spacecraft operations phase Context triple: [Soyuz program (space station operations phase), instanceOf, spacecraft operations phase]
-
A.
spaceflight program phase
chosen
A spaceflight program phase is a distinct, time-bounded stage within a space mission or program that groups related objectives, activities, and resources to achieve specific milestones in the overall mission lifecycle.
-
B.
space operations
Space operations encompass the planning, execution, and management of activities involving spacecraft, satellites, and related systems to support missions such as communication, navigation, exploration, and defense in the space environment.
-
C.
space operations command
A space operations command is a military or governmental organizational unit responsible for planning, directing, and controlling space-based assets and activities to support national security, communications, navigation, and situational awareness.
-
D.
space operations center
A space operations center is a specialized facility that monitors, controls, and coordinates spacecraft, satellites, and related space missions in real time.
-
E.
spaceflight procedure
A spaceflight procedure is a formally defined, step-by-step set of actions and decision rules that astronauts, ground controllers, or automated systems follow to safely and reliably conduct specific operations during a space mission.
- 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.