Triple
T336733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Atmosphere Watch |
E6744
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | atmospheric monitoring programme |
C656
|
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: atmospheric monitoring programme Context triple: [Global Atmosphere Watch, instanceOf, atmospheric monitoring programme]
-
A.
aircraft observation organisation
An aircraft observation organisation is an entity responsible for systematically monitoring, recording, and analyzing aircraft movements and related airspace activities for purposes such as safety, research, regulation, or intelligence.
-
B.
meteorological organization
chosen
A meteorological organization is an entity responsible for observing, analyzing, and forecasting atmospheric conditions to support weather prediction, climate monitoring, and related public and scientific services.
-
C.
astronomical observatory
An astronomical observatory is a facility equipped with specialized instruments and structures designed to observe, record, and analyze celestial objects and phenomena.
-
D.
NASA mission component
A NASA mission component is a distinct hardware, software, or operational element designed to perform a specific function that contributes to the overall objectives and success of a NASA space mission.
-
E.
integrated air defence system
An integrated air defence system is a coordinated network of sensors, command and control elements, and weapon systems designed to detect, track, and engage aerial threats to protect designated airspace and assets.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.