Triple
T36709742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Remote Sensing Centre |
E906763
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | remote sensing agency |
C1669
|
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 agency Context triple: [National Remote Sensing Centre, instanceOf, remote sensing agency]
-
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.
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.
-
D.
space agency
chosen
A space agency is an organization, typically government-funded, responsible for planning, developing, and conducting space missions, research, and related technologies.
-
E.
remote sensing satellite constellation
A remote sensing satellite constellation is a coordinated network of satellites designed to collect and transmit Earth observation data—such as imagery, environmental measurements, and geospatial information—at high temporal and spatial resolution.
- 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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.