Triple
T2121206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saffir–Simpson Hurricane Wind Scale |
E43925
|
entity |
| Predicate | usedForWarning |
P98
|
FINISHED |
| Object | hurricane preparedness |
—
|
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: hurricane preparedness | Statement: [Saffir–Simpson Hurricane Wind Scale, usedForWarning, hurricane preparedness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForWarning Context triple: [Saffir–Simpson Hurricane Wind Scale, usedForWarning, hurricane preparedness]
-
A.
usedFor
chosen
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
B.
warnsAbout
Indicates that one entity alerts or cautions another entity about a potential danger, risk, or problem.
-
C.
usedInsteadOf
Indicates that one entity is employed or chosen as a substitute or replacement for another entity.
-
D.
usedInCase
Indicates that something (such as an item, method, or piece of information) is employed or applied within a particular case or instance.
-
E.
warnedWith
Indicates that one entity issued a warning to another entity using or accompanied by a particular medium, content, or instrument.
- 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_69a88717cfe48190b7ecdd68c824848a |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb3404348190bc843022fbd2b4d0 |
completed | March 7, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69abb7bbf9d881909d223b0cab7cab18 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.