Will Google release Gemini 3.5 Pro before Aug 31, 2026
event base · KXGEMINI
Term structure
YES probability across 11 tenors
Analysis
The Will Google release Gemini 3.5 Pro before Aug 31, 2026 family contains 22 contracts spread across 11 tenors (5d – 4mo). The average implied YES probability is 29.6%.
A bespoke narrative analysis is generated by an LLM on a 24h cron when the constituent set changes. If this paragraph is showing instead, the curve has either just appeared in the index or has not yet been queued.
Constituent markets
22 kalshi contracts
How to read this page
A term structure plots the implied YES probability of each constituent market against its days-to-resolution. Steepening upward = the market prices the event as becoming more likely with time. Flat = stable expectations. Inverted = a near-term catalyst raises odds early then they fade.
Curve construction: each constituent contract is identified by its venue event_id (KXGEMINI on kalshi). Tenor is computed from the contract’s close_time minus snapshot time, rounded to days. We do not interpolate between tenors — every plotted point is a real, traded contract. Outcome-slate pages show price-as-probability for mutually-exclusive contracts; term-structure pages show price-as-probability vs days-to-resolution for the same underlying event.
How we compute these odds
SimpleFunctions aggregates live prediction-market contracts from Kalshi and Polymarket. Each slug groups contracts that resolve on the same underlying event, identified by venue event_id.
For binary slugs, the headline probability is the liquidity-weighted mid-price across all bound contracts. For multi-outcome slugs (e.g. elections with 3+ candidates), the headline is the leader’s price; we never arithmetically average disjoint outcomes — that would produce a number with no real-world meaning.
Snapshots refresh every 5 minutes during market hours; daily aggregates are computed at 04:00 UTC. The 30-day sparkline is drawn from per-ticker daily means stored in market_indicator_daily; 24h delta and movement events are derived from the same source.