Triple
T1841114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Storm Prediction Center |
E41177
|
entity |
| Predicate | typeOfForecasts |
P34023
|
FINISHED |
| Object | day 1 convective outlooks |
—
|
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: day 1 convective outlooks | Statement: [Storm Prediction Center, typeOfForecasts, day 1 convective outlooks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfForecasts Context triple: [Storm Prediction Center, typeOfForecasts, day 1 convective outlooks]
-
A.
weatherCondition
Indicates the type of atmospheric state or weather pattern (e.g., sunny, rainy, snowy) affecting a location or time period.
-
B.
typicalStormType
Indicates the kind of storm that is most commonly or characteristically associated with a given context or location.
-
C.
hasWeather
Indicates that a location or environment is experiencing or characterized by a particular type of weather condition.
-
D.
climatologicalType
Indicates the classification of a climate or weather pattern that characterizes a place, period, or condition.
-
E.
typicalEnsembleType
Indicates the usual or characteristic type of ensemble associated with or used to perform a given work, piece, or musical context.
- 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_69a88647f9388190909bc36e795bdaec |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdb0d2c8190a67f584e67979fa3 |
completed | March 7, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69abb32a8d548190a231c7c2ce276a5e |
completed | March 7, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:33 p.m.