Triple
T10548213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voyager 1 flight data system |
E248876
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | telemetry and data handling subsystem |
C7918
|
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: telemetry and data handling subsystem Context triple: [Voyager 1 flight data system, instanceOf, telemetry and data handling subsystem]
-
A.
telemetry service
A telemetry service is a system component that collects, transmits, stores, and analyzes operational and performance data from distributed applications or devices to enable monitoring, diagnostics, and optimization.
-
B.
radar subsystem
A radar subsystem is a component of a larger system that generates, transmits, receives, and processes radio-frequency signals to detect, locate, and track objects in its environment.
-
C.
Voyager subsystem
chosen
A Voyager subsystem is a modular component within the Voyager architecture responsible for a specific set of functions, resources, or services that collectively support the system’s overall mission and operation.
-
D.
centralized monitoring center
A centralized monitoring center is a dedicated facility that aggregates, analyzes, and manages real-time data and alerts from distributed systems or locations to enable coordinated oversight and rapid response.
-
E.
environmental sensor suite
An environmental sensor suite is an integrated collection of sensors and supporting electronics designed to measure, process, and report multiple environmental parameters such as temperature, humidity, air quality, light, and pressure in a coordinated manner.
- 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:33 p.m.