Triple
T20805246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurricane Ophelia (2005) |
E512137
|
entity |
| Predicate | peakSustainedWinds |
P40034
|
FINISHED |
| Object | 85 mph |
—
|
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: 85 mph | Statement: [Hurricane Ophelia (2005), peakSustainedWinds, 85 mph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakSustainedWinds Context triple: [Hurricane Ophelia (2005), peakSustainedWinds, 85 mph]
-
A.
maximumSustainedWinds
chosen
Indicates the highest wind speed that is maintained continuously over a specified averaging period, rather than in brief gusts.
-
B.
maximumGusts
Indicates the relationship where a recorded wind gust value represents the highest (maximum) gust observed within a specified time or context.
-
C.
windSpeed
Indicates the measured or estimated rate at which wind is moving at a given location and time.
-
D.
prevailingSurfaceWinds
Indicates the typical or most frequently occurring wind direction and speed that dominate at a given location over a specified period.
-
E.
strongestStorm
Indicates that one storm is the most intense or powerful compared to a set of other storms.
- 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_69e0b4cc69f481908e98751e697b9df4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2cf1cbc819092d92625dfb107d0 |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:40 p.m.