Triple
T32256893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPOT Image |
E824049
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | remote sensing company |
C33874
|
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: remote sensing company Context triple: [SPOT Image, instanceOf, remote sensing company]
-
A.
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.
-
B.
remote sensing mission
A remote sensing mission is an organized effort that uses satellite or airborne sensors to systematically collect, transmit, and analyze data about the Earth's surface, atmosphere, or oceans without direct physical contact.
-
C.
geospatial company
chosen
A geospatial company is an organization that collects, analyzes, and applies location-based data and mapping technologies to provide insights, products, and services related to the Earth's surface and spatial relationships.
-
D.
remote sensing technique
A remote sensing technique is a method for acquiring information about objects or areas from a distance, typically using satellite or airborne sensors that detect and measure reflected or emitted electromagnetic radiation.
-
E.
remote sensing experiment
A remote sensing experiment is a systematic investigation that uses sensors on satellites, aircraft, or ground-based platforms to collect and analyze data about the Earth's surface or atmosphere without direct physical contact.
- 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.