Triple

T37649426
Position Surface form Disambiguated ID Type / Status
Subject Storm Desmond E937130 entity
Predicate meteorologicalType P188561 FINISHED
Object deep Atlantic low-pressure system 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: deep Atlantic low-pressure system | Statement: [Storm Desmond, meteorologicalType, deep Atlantic low-pressure system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: meteorologicalType
Context triple: [Storm Desmond, meteorologicalType, deep Atlantic low-pressure system]
  • A. climatologicalType
    Indicates the classification of a climate or weather pattern that characterizes a place, period, or condition.
  • B. meteorologicalOrigin
    Indicates that one entity originates from, is caused by, or is derived from a particular meteorological or weather-related phenomenon.
  • C. meteorologicalStatus
    Indicates the current or historical weather-related condition or state affecting an entity or location.
  • D. typicalWeatherFeature
    Indicates a weather condition or pattern that commonly characterizes a place or time period.
  • E. stormTypeWhenUsed
    Indicates the specific type or category of storm associated with or triggered when a particular thing is used.
  • F. None of above. chosen

Provenance (4 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_69f76ed4fe908190b8061c5c135e0971 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fbaa19e4a88190b04f26c0d4e708fd completed May 6, 2026, 8:52 p.m.
PD Predicate disambiguation batch_69fba8860f98819080b7bab05837b974 completed May 6, 2026, 8:45 p.m.
PDg Predicate description generation batch_69fbaa108ee48190b84d13df3ef3e365 completed May 6, 2026, 8:52 p.m.
Created at: May 3, 2026, 4:18 p.m.