Triple
T27648876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Storm Desmond |
E696790
|
entity |
| Predicate | maximumDailyRainfallRecord |
P117956
|
FINISHED |
| Object | 341.4 millimetres at Honister Pass |
—
|
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: 341.4 millimetres at Honister Pass | Statement: [Storm Desmond, maximumDailyRainfallRecord, 341.4 millimetres at Honister Pass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumDailyRainfallRecord Context triple: [Storm Desmond, maximumDailyRainfallRecord, 341.4 millimetres at Honister Pass]
-
A.
rainfallPeak
Indicates the time or value at which rainfall intensity reaches its maximum during a given period or event.
-
B.
rainfallMaxLocation
chosen
Indicates the location at which the maximum amount of rainfall is observed or recorded.
-
C.
maximumRecordedTemperature
Indicates the highest temperature value that has been observed and recorded for a given entity or context.
-
D.
snowfallRecord
Indicates that a specific amount of snow has been measured or documented for a particular place and time.
-
E.
floodRecord
Indicates that an entity serves as a documented record or report of a flood event affecting another entity or area.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 27, 2026, 2:31 p.m.