Triple
T30235792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WMO-No. 558 |
E768761
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | meteorological regulations manual |
C57169
|
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: meteorological regulations manual Context triple: [WMO-No. 558, instanceOf, meteorological regulations manual]
-
A.
meteorological regulation
Meteorological regulation is the systematic control, coordination, and oversight of weather-related activities, data, and services to ensure safety, compliance, and effective management of atmospheric conditions and their impacts.
-
B.
meteorological standard
A meteorological standard is an agreed-upon set of definitions, measurements, instruments, and procedures that ensure consistency and comparability of weather and climate observations across different locations and times.
-
C.
meteorological organization
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.
-
D.
meteorological infrastructure
Meteorological infrastructure comprises the interconnected network of instruments, stations, communication systems, and data-processing facilities used to observe, measure, and analyze atmospheric conditions for weather forecasting and climate monitoring.
-
E.
meteorology book
A meteorology book is a comprehensive text that explains the science of the atmosphere, weather processes, and climate phenomena, often combining theory, data, and practical forecasting techniques.
- F. None of above. chosen
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_69f224820c048190b1435c4cc145acf1 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:37 p.m.