Triple
T8261429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurricane Irma |
E193203
|
entity |
| Predicate | maximumSustainedWinds_mph |
P40034
|
FINISHED |
| Object | 180 |
—
|
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: 180 | Statement: [Hurricane Irma, maximumSustainedWinds_mph, 180]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumSustainedWinds_mph Context triple: [Hurricane Irma, maximumSustainedWinds_mph, 180]
-
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.
strongestStorm
Indicates that one storm is the most intense or powerful compared to a set of other storms.
-
D.
landfallIntensity
Indicates the strength or magnitude of a storm system at the time and location where it first makes landfall.
-
E.
dateOfLandfall
Indicates the specific calendar date on which a storm or similar event first makes landfall at a particular location.
- 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_69ca82e081d48190986beaa51f498ab9 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7936b72c8190b998da033df611d1 |
completed | March 31, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69cb36b8707881909aca349230495a5a |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:49 p.m.