Triple
T23737077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mission Control Centres |
E586567
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space operations infrastructure |
C34654
|
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: space operations infrastructure Context triple: [Mission Control Centres, instanceOf, space operations infrastructure]
-
A.
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.
-
B.
space operations center
chosen
A space operations center is a specialized facility that monitors, controls, and coordinates spacecraft, satellites, and related space missions in real time.
-
C.
space infrastructure project
A space infrastructure project is a large-scale, coordinated initiative to design, build, and operate physical and digital systems that enable sustained activities and services in space, such as communication, transportation, energy, and research.
-
D.
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.
-
E.
space launch facility
A space launch facility is a specialized complex equipped with infrastructure, systems, and support services for preparing, launching, and sometimes recovering spacecraft and launch vehicles.
- 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 7:10 p.m.