The normalized evidence record is visible; the complete 221-row extraction is not recoverable from the audit link alone

The earlier JSON exposes raw evidence under each restaurant’s signals array, with separate occasion annotations and judgments. The linked artifact currently resolves to report metadata rather than a downloadable copy of every candidate extraction row.

221
candidate extraction rows reported in the prior run
1
normalized signal visibly preserved in the supplied excerpt
3
separate layers: signals, annotations, judgments

What “raw” means in this result

evidence lineage
Retrieved candidate rows
Search URLs and semantic extraction output
Normalized signals
Quoted, entity-bound evidence with source metadata
Occasion annotations
Support, counter, neutral or mixed for anniversary.couple
Judgments and admission
Fit inference, confidence, unknowns and eligibility
Normalized signal schema availableyes
Complete candidate-row export available from audit URLno

Findings

  1. The reusable raw layer is restaurants[].signals[]. It contains the source URL, excerpt, predicate, evidence class, date, binding confidence, daypart, freshness and structured value.
  2. Occasion interpretation is deliberately separate. The matching annotations[] entry carries anniversary-specific polarity and dimensions without contaminating the evidence record.
  3. The audit link is not the complete export. Fetching it returned artifact metadata—title, size and expiry—not the underlying 221 candidate rows. webql.keenable.ai

Visible raw-record example

FieldValue preserved in the supplied result
signal_iduchi-s1
predicatelogistics.arrival_friction
classreported_experience
excerpt“We had table reservations for 9, at 9:20, we still weren’t sat.”
structured valueA diner reported waiting at least 20 minutes beyond a 9 p.m. reservation.
daypart / freshnessdinner / current
Method: inspected the one supplied artifact URL on 2026-08-25 and compared its returned metadata with the raw-signal excerpt preserved in the conversation. The 221 figure is the prior run’s reported candidate-row count, not a newly reconstructed export.
Keenable · made with SELECT* · 1 page in 33s · Open the chatShare: XLinkedInReddit