Triple
T15829756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DLR integration and test facilities |
E383838
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space systems ground infrastructure |
C6199
|
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 systems ground infrastructure Context triple: [DLR integration and test facilities, instanceOf, space systems ground infrastructure]
-
A.
space communication network
A space communication network is an interconnected system of ground stations, satellites, and relay nodes that enables the reliable transmission, routing, and reception of data across space and between space-based and terrestrial assets.
-
B.
ground segment equipment
chosen
Ground segment equipment comprises the terrestrial hardware and software systems that support, control, communicate with, and process data from space-based assets such as satellites.
-
C.
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.
-
D.
deep space communications facility
A deep space communications facility is a ground-based complex equipped with large antennas, high-power transmitters, and sensitive receivers used to send commands to and receive data from spacecraft operating far beyond Earth's orbit.
-
E.
NASA ground support equipment
NASA ground support equipment comprises the specialized tools, structures, and systems used on the ground to assemble, test, transport, service, and launch spacecraft and launch vehicles safely and reliably.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:49 a.m.