Triple
T6204743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madrid Deep Space Communications Complex |
E138719
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space communications facility |
C7369
|
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 communications facility Context triple: [Madrid Deep Space Communications Complex, instanceOf, space communications facility]
-
A.
space communication network
chosen
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.
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.
-
C.
space communication project
A space communication project is an organized effort to design, develop, and operate systems that enable reliable data and signal exchange between spacecraft, satellites, and ground stations.
-
D.
spaceport facility
A spaceport facility is a complex of specialized infrastructure and services designed to support the launch, landing, maintenance, and logistical operations of spacecraft and their crews.
-
E.
ESA facility
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.
- 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_69c008acbea48190991c6b834bb45d65 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:20 p.m.