Triple
T7887949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurricane Michael |
E183151
|
entity |
| Predicate | landfallIntensity |
P79576
|
FINISHED |
| Object | Category 5 |
—
|
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: Category 5 | Statement: [Hurricane Michael, landfallIntensity, Category 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landfallIntensity Context triple: [Hurricane Michael, landfallIntensity, Category 5]
-
A.
landfallLocation
Indicates the geographic location where a storm or similar weather system first makes landfall.
-
B.
maximumSustainedWinds
Indicates the highest wind speed that is maintained continuously over a specified averaging period, rather than in brief gusts.
-
C.
dateOfLandfall
Indicates the specific calendar date on which a storm or similar event first makes landfall at a particular location.
-
D.
rankByAtlanticHurricaneIntensity
Indicates the ordering of entities based on the strength or severity of Atlantic hurricanes associated with them.
-
E.
firstLandfallBy
Indicates the location or entity where something (typically a storm, traveler, or object) initially makes landfall or first arrives from a journey over water or air.
- 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_69ca828af6e48190a06ee7010d8f0e64 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39d97460819089e37169813af5c2 |
completed | March 31, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69cae92b0cd881908e715a10d3252e83 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf786ec748190b6347b0c94335550 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:59 p.m.