Triple
T27752221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaisalmer wind farms |
E701240
|
entity |
| Predicate | regionWindCharacteristic |
P74831
|
FINISHED |
| Object | high wind potential |
—
|
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: high wind potential | Statement: [Jaisalmer wind farms, regionWindCharacteristic, high wind potential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionWindCharacteristic Context triple: [Jaisalmer wind farms, regionWindCharacteristic, high wind potential]
-
A.
windCharacteristics
chosen
Indicates the specific properties or qualities that describe the behavior and nature of the wind in a given context.
-
B.
hasExtremeWeatherCharacteristic
Indicates that something possesses a notable or defining feature related to extreme weather conditions.
-
C.
typicalWeatherFeature
Indicates a weather condition or pattern that commonly characterizes a place or time period.
-
D.
typicalWindStrength
Indicates the usual or characteristic intensity of wind associated with something, such as a place, time, or condition.
-
E.
windSpeed
Indicates the measured or estimated rate at which wind is moving at a given location and time.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: April 27, 2026, 4:21 p.m.