Triple
T20805322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tropical Storm Arlene (2005) |
E512138
|
entity |
| Predicate | windEffect |
P74831
|
FINISHED |
| Object | strong wind gusts in coastal regions |
—
|
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: strong wind gusts in coastal regions | Statement: [Tropical Storm Arlene (2005), windEffect, strong wind gusts in coastal regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: windEffect Context triple: [Tropical Storm Arlene (2005), windEffect, strong wind gusts in coastal regions]
-
A.
windSpeed
Indicates the measured or estimated rate at which wind is moving at a given location and time.
-
B.
windResistance
Indicates the degree to which an entity opposes or reduces the effect of wind acting upon it.
-
C.
windCharacteristics
chosen
Indicates the specific properties or qualities that describe the behavior and nature of the wind in a given context.
-
D.
fireEffect
Indicates that one entity produces, causes, or is associated with a fire-related impact or consequence on another entity.
-
E.
breathEffect
Indicates an effect or change that occurs as a direct result of an entity’s breath.
- 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_69e0b4cc69f481908e98751e697b9df4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2cf1cbc819092d92625dfb107d0 |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:40 p.m.