Triple
T32256825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HRG (High Resolution Geometric) |
E824047
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Earth observation sensor |
C52751
|
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: Earth observation sensor Context triple: [HRG (High Resolution Geometric), instanceOf, Earth observation sensor]
-
A.
Earth observation instrument package
chosen
An Earth observation instrument package is an integrated set of sensors and supporting hardware designed to collect, process, and transmit measurements of the Earth's atmosphere, land, and oceans from spaceborne or airborne platforms.
-
B.
space surveillance sensor
A space surveillance sensor is a device or system that detects, tracks, and characterizes objects in space to support situational awareness, collision avoidance, and space traffic management.
-
C.
remote sensing satellite
A remote sensing satellite is an orbiting spacecraft equipped with sensors that collect data about the Earth's surface and atmosphere for applications such as mapping, environmental monitoring, and resource management.
-
D.
Earth observation data access tool
A software system that enables users to discover, query, and retrieve Earth observation datasets from various sensors and repositories through a unified, user-friendly interface.
-
E.
satellite-based Earth observation service
A satellite-based Earth observation service collects, processes, and delivers remotely sensed data about the Earth's surface and atmosphere to support applications such as environmental monitoring, resource management, and disaster response.
- 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:41 a.m.