Triple
T17131417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESA ESTRACK network |
E415728
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | spacecraft tracking network |
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: spacecraft tracking network Context triple: [ESA ESTRACK network, instanceOf, spacecraft tracking network]
-
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.
satellite tracking system
A satellite tracking system is a coordinated set of hardware and software components that continuously determine, monitor, and predict the position and trajectory of satellites in orbit for communication, navigation, and control purposes.
-
C.
ground tracking facility
A ground tracking facility is a terrestrial station equipped with antennas, sensors, and communication systems used to monitor, communicate with, and control spacecraft or other remote vehicles.
-
D.
NASA network
A NASA network is an interconnected system of communication, data, and computing resources that links NASA’s spacecraft, ground stations, research centers, and partner organizations to support space missions and scientific operations.
-
E.
satellite system
A satellite system is an integrated network of orbiting spacecraft, ground stations, and communication links designed to perform functions such as communication, navigation, Earth observation, or scientific research.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:36 a.m.