Triple
T7887973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurricane Michael |
E183151
|
entity |
| Predicate | upgradedToCategory5 |
P23033
|
FINISHED |
| Object | 2019-04-19 |
—
|
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: 2019-04-19 | Statement: [Hurricane Michael, upgradedToCategory5, 2019-04-19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upgradedToCategory5 Context triple: [Hurricane Michael, upgradedToCategory5, 2019-04-19]
-
A.
reachedCategory5On
chosen
Indicates that an entity attained Category 5 intensity or status on a specific date or at a specific time.
-
B.
upgradedBy
Indicates that an entity has been improved, enhanced, or moved to a higher version or level as a result of actions performed by another entity.
-
C.
hasUpgrade
Indicates that one entity possesses, includes, or is associated with an improved or enhanced version of another entity.
-
D.
upgradeOf
Indicates that one entity is a newer, improved, or more advanced version of another entity.
-
E.
partlyUpgradedTo
Indicates that an entity has undergone an incomplete or partial upgrade to another specified state, version, or configuration.
- 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_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. |
Created at: March 30, 2026, 4:59 p.m.