Triple
T8514481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RSMC Moscow (space weather centre) |
E201537
|
entity |
| Predicate | typeOfForecast |
P34023
|
FINISHED |
| Object | short-term space weather forecast |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: short-term space weather forecast | Statement: [RSMC Moscow (space weather centre), typeOfForecast, short-term space weather forecast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfForecast Context triple: [RSMC Moscow (space weather centre), typeOfForecast, short-term space weather forecast]
-
A.
typeOfForecasts
chosen
Indicates the specific kinds or categories of forecasts associated with or produced by an entity.
-
B.
weatherCondition
Indicates the type of atmospheric state or weather pattern (e.g., sunny, rainy, snowy) affecting a location or time period.
-
C.
forecastUsing
Indicates that one entity generates or derives a forecast by using information, methods, or data from another entity.
-
D.
weatherRole
Indicates a role or function that an entity has in relation to weather conditions or weather-related phenomena.
-
E.
drivesWeather
Indicates that one factor or process causally influences or determines weather conditions.
- F. None of above.
Provenance (3 batches)
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_69ca8320e5748190ac2c585a0bba8193 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe60e12848190a4a3dfa457aef275 |
completed | March 31, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69cbd10cfd208190a519049fad32c508 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:15 p.m.