Triple
T15829726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DLR Galileo Control Center |
E383837
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Galileo ground segment facility |
C14251
|
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: Galileo ground segment facility Context triple: [DLR Galileo Control Center, instanceOf, Galileo ground segment facility]
-
A.
ESA facility
chosen
An ESA facility is a specialized location, infrastructure, or installation operated or supported by the European Space Agency to conduct space-related research, development, testing, mission operations, or support services.
-
B.
DLR station
A DLR station is a designated stop or terminal along the Docklands Light Railway network where passengers can board, alight, and transfer between automated light rail services.
-
C.
CNES facility
A CNES facility is a specialized site operated by the French space agency (CNES) that supports the development, testing, launch, tracking, and control of space missions and related aerospace activities.
-
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.
division of the European Southern Observatory
A division of the European Southern Observatory is an organizational unit within ESO responsible for a specific set of scientific, technical, or administrative functions that support the observatory’s mission to design, operate, and exploit world-class astronomical facilities.
- 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.