Triple
T15461286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diego Garcia Tracking Station |
E371904
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ground tracking station |
C17219
|
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: ground tracking station Context triple: [Diego Garcia Tracking Station, instanceOf, ground tracking station]
-
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.
ground segment equipment
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.
surface station
chosen
A surface station is a ground-based facility equipped with instruments and systems to monitor, control, or communicate with external environments or assets such as weather, spacecraft, or remote sensors.
-
D.
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.
-
E.
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.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3:32 a.m.