Triple
T18708313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurricane Andrew |
E457431
|
entity |
| Predicate | becameHurricaneOn |
P40033
|
FINISHED |
| Object | 1992-08-22 |
—
|
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: 1992-08-22 | Statement: [Hurricane Andrew, becameHurricaneOn, 1992-08-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameHurricaneOn Context triple: [Hurricane Andrew, becameHurricaneOn, 1992-08-22]
-
A.
reachedHurricaneStatusOn
chosen
Indicates the date or time at which a storm system intensified enough to be classified as a hurricane.
-
B.
reachedTropicalStormStatusOn
Indicates the date or time at which something, typically a weather system, attained tropical storm intensity or classification.
-
C.
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.
-
D.
dateOfLandfall
Indicates the specific calendar date on which a storm or similar event first makes landfall at a particular location.
-
E.
firstLandfallYear
Indicates the calendar year in which something (typically a storm or similar event) first makes landfall.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56719383481909d68c9e873ca0800 |
completed | April 19, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:50 a.m.