Triple
T23486967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DSS-14 |
E570560
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | deep space communication antenna |
C33034
|
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: deep space communication antenna Context triple: [DSS-14, instanceOf, deep space communication antenna]
-
A.
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.
-
B.
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.
-
C.
parabolic antenna
chosen
A parabolic antenna is a high-gain directional antenna that uses a parabolic reflector to focus incoming or outgoing radio waves into a narrow beam for long-distance communication or signal reception.
-
D.
VLBI radio satellite
A VLBI radio satellite is a space-based observatory that precisely records radio signals from cosmic sources in coordination with ground telescopes to form an extremely large virtual antenna for high-resolution astronomical imaging and measurements.
-
E.
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.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 6:04 p.m.