Triple
T2121197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saffir–Simpson Hurricane Wind Scale |
E43925
|
entity |
| Predicate | doesNotDirectlyMeasure |
P7357
|
FINISHED |
| Object | storm surge |
—
|
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: storm surge | Statement: [Saffir–Simpson Hurricane Wind Scale, doesNotDirectlyMeasure, storm surge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotDirectlyMeasure Context triple: [Saffir–Simpson Hurricane Wind Scale, doesNotDirectlyMeasure, storm surge]
-
A.
doesNotMeasure
chosen
Indicates that an entity is not used to quantify, assess, or determine the value or extent of another entity or property.
-
B.
doesNotDirectlyRegulate
Indicates that one entity has no immediate or primary regulatory control or influence over another entity or process.
-
C.
doesNotDetermine
Indicates that one entity or factor does not uniquely fix, decide, or specify the state, value, or outcome of another.
-
D.
doesNotProduce
Indicates that one entity fails to generate, create, or yield another entity or outcome.
-
E.
doesNotUse
Indicates that one entity intentionally refrains from employing, utilizing, or relying on another entity, method, or resource.
- 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.