entity, theme, window, and role, or pass similar_to a unit id to find more like it.
The recipe
A retrieval is shaped by three kinds of controls:- Filters narrow what is eligible:
entity,theme,window,role, andcontent_type. - Query mode sets what you match on: a natural-language question, or
similar_toa unit id for more-like-this. - Ranking reorders the results:
recency_boostanddiversity_cap.
1
Search your scope
A natural-language query, narrowed by
entity, theme, and window to your scope.2
Filter by role
Pull one layer of the decomposition with
role: thesis / synopsis (the central position), argument (the reasoning), or claim (atomic factual assertions).3
Find more like this
Pass
similar_to a unit id to get embedding-backed “more like this”: the cluster of units making the same point, across independent sources.4
Tune the ranking
recency_boost favors newer signals; diversity_cap limits units per source, so one prolific author can’t dominate the results.5
Split by content type, then drill
signals.list takes content_type to separate event (what happened) from analysis (what experts think). Pull either, then fetch any signal’s full verified decomposition as a flat units[] with roles and evidence.gildea, set GILDEA_API_KEY, then (pure SDK, no model calls):
What you get
The verified units in yourscope, each with its citation, determined by the filters, query mode, and ranking options you chose. Trace any unit to its source or embed it beside your own data.