Human Feedback Types
strongPairwise Preference
Directly usable for protocol triage.
"Conversational data is increasingly used as a persistent source of user state for long-running assistants and AI agents."
HFEPX · Eval paper review
Maolin Wang, Yu Wang, Zichun Liu, Baiyuan Qiu +4 more
Published
Jul 1, 2026
Citations
0
Trust level
Moderate
Usefulness score
65/100 (Medium)
Extraction confidence
70% (Moderate)
Derived from extracted protocol signals and abstract evidence.
Rater population
Not reported
Signals refreshed
Jul 1, 2026
This paper has useful evaluation signal, but protocol completeness is partial; pair it with related papers before deciding implementation strategy.
Use this for comparison and orientation, not as your only source.
Best use
Secondary protocol comparison source
Use if you need
A secondary eval reference to pair with stronger protocol papers.
What to verify
Validate the evaluation procedure and quality controls in the full paper before operational use.
Main weakness
No major weakness surfaced.
Useful as a secondary reference; validate protocol details against neighboring papers.
If you are doing eval pipeline work, start here
Conversational data is increasingly used as a persistent source of user state for long-running assistants and AI agents. However, querying this data remains challenging because conversations naturally evolve: plans are revised, preferences change, and later messages frequently supersede or contradict earlier information. Existing long-memory pipelines largely treat memories as independent text or vector objects. This approach often retrieves semantically similar but stale evidence, offering limited support for state-aware reasoning. To address this problem, we present TRACE, a query processing framework over temporal evidence graphs for evolving conversational data. TRACE models conversations as a hierarchical graph spanning events, sessions, and topics, enriched with typed temporal, causal, update, and contradiction relations. Crucially, the framework maintains validity annotations so obsolete facts remain accessible for historical queries but are discounted for current-state answers. At query time, TRACE combines vector-based note retrieval with graph-guided evidence search, generating validity-aware support paths and a hybrid context for answer generation. This design separates lexical recall from evidence reconstruction, enabling bounded query-time reasoning over long conversational histories. Experiments on long-conversation query-answering (QA) benchmarks show that TRACE improves temporal and multi-hop reasoning, with ablations highlighting the importance of hierarchy, update-aware seeding, and path-grounded evidence.
These are the protocol signals we could actually recover from the available paper metadata. Use them to decide whether this paper is worth deeper reading.
Pairwise Preference
Directly usable for protocol triage.
"Conversational data is increasingly used as a persistent source of user state for long-running assistants and AI agents."
Automatic Metrics
Includes extracted eval setup.
"Conversational data is increasingly used as a persistent source of user state for long-running assistants and AI agents."
Not reported
No explicit QC controls found.
"Conversational data is increasingly used as a persistent source of user state for long-running assistants and AI agents."
Not extracted
No benchmark anchors detected.
"Conversational data is increasingly used as a persistent source of user state for long-running assistants and AI agents."
Recall
Useful for evaluation criteria comparison.
"This design separates lexical recall from evidence reconstruction, enabling bounded query-time reasoning over long conversational histories."
No benchmark or dataset names were extracted from the available abstract.
Conversational data is increasingly used as a persistent source of user state for long-running assistants and AI agents.
Based on abstract + metadata only. Check the source paper before making high-confidence protocol decisions.
Human feedback protocol is explicit
Detected: Pairwise Preference
Evaluation mode is explicit
Detected: Automatic Metrics
Quality control reporting appears
No calibration/adjudication/IAA control explicitly detected.
Benchmark or dataset anchors are present
No benchmark/dataset anchor extracted from abstract.
Metric reporting is present
Detected: recall