Triple
T8377254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RSMC Toulouse (space weather centre) |
E197606
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space weather centre |
C9199
|
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: space weather centre Context triple: [RSMC Toulouse (space weather centre), instanceOf, space weather centre]
-
A.
space weather prediction agency
chosen
A space weather prediction agency is an organization that monitors solar and geomagnetic activity to forecast space weather events and provide warnings to protect satellites, power grids, communications, and other vulnerable technologies.
-
B.
ionospheric research center
An ionospheric research center is a specialized facility that studies the Earth's ionosphere and its interactions with solar and geomagnetic activity to improve understanding of radio wave propagation, space weather, and related atmospheric phenomena.
-
C.
space research centre
A space research centre is an institution dedicated to the scientific study, exploration, and technological development related to outer space and celestial phenomena.
-
D.
heliophysics mission fleet
A heliophysics mission fleet is a coordinated collection of spacecraft and instruments designed to observe the Sun and its interactions with the solar system from multiple vantage points to better understand solar activity and space weather.
-
E.
space science division
The space science division is an organizational unit dedicated to researching, analyzing, and advancing knowledge about outer space, celestial bodies, and related physical phenomena.
- 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_69ca82f64c188190af4e1608036b865d |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 6:02 p.m.