Triple
T14907826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Levante |
E371180
|
entity |
| Predicate | windSpeedRange |
P60166
|
FINISHED |
| Object | moderate to strong |
—
|
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: moderate to strong | Statement: [Levante, windSpeedRange, moderate to strong]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: windSpeedRange Context triple: [Levante, windSpeedRange, moderate to strong]
-
A.
windSpeed
chosen
Indicates the measured or estimated rate at which wind is moving at a given location and time.
-
B.
windCharacteristics
Indicates the specific properties or qualities that describe the behavior and nature of the wind in a given context.
-
C.
typicalWindStrength
Indicates the usual or characteristic intensity of wind associated with something, such as a place, time, or condition.
-
D.
windChill
Indicates the perceived decrease in air temperature felt by a body due to the combined effect of wind speed and actual air temperature.
-
E.
maximumGusts
Indicates the relationship where a recorded wind gust value represents the highest (maximum) gust observed within a specified time or context.
- 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded61b3c808190b4f6df4e5cb401ad |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a4a14a88190951bb8f4c60bd37b |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:23 a.m.