Triple
T9808168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RCM |
E238203
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | radar imaging satellite system |
C23970
|
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: radar imaging satellite system Context triple: [RCM, instanceOf, radar imaging satellite system]
-
A.
military satellite
A military satellite is an artificial satellite deployed and operated by armed forces to support defense-related functions such as reconnaissance, communications, navigation, early warning, and targeting.
-
B.
military radar system
A military radar system is an integrated sensor platform that emits and receives electromagnetic signals to detect, track, and classify airborne, maritime, or ground targets for surveillance, targeting, and defense operations.
-
C.
spaceborne radiometer
A spaceborne radiometer is an instrument mounted on a satellite that measures the intensity of electromagnetic radiation emitted, reflected, or scattered by the Earth or other celestial bodies to infer physical properties such as temperature, composition, and surface characteristics.
-
D.
radar system family
A radar system family is a group of related radar systems that share a common architecture, technology base, and design principles while differing in specific capabilities, configurations, or applications.
-
E.
polar-orbiting satellite
chosen
A polar-orbiting satellite is a spacecraft that travels in a low Earth orbit passing close to the poles, allowing it to observe the entire Earth's surface over time as the planet rotates beneath it.
- 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_69ca84defac48190abc1148804f184c1 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:29 p.m.