You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Treat `N/A` confidence/salience as **unknown** — set those fields to `null`
104
+
in the `duplicate_groups` output (do NOT omit the keys); the pipeline will
105
+
fall back to `max(source.confidence)` / `max(source.salience)`.
106
106
- Treat `N/A` created_at as **older than any real timestamp** for
107
107
winner-selection purposes (a fact with a real date beats one with N/A).
108
108
@@ -121,9 +121,9 @@ You must output ONLY valid JSON matching this exact schema. No preamble, no expl
121
121
"kept_ids": ["<id>", "<id>"]
122
122
}
123
123
```
124
-
<!-- confidence/salience: float 0..1, or omit the field if unknown -->
124
+
<!-- confidence/salience: float 0..1, or null if you cannot infer -->
125
125
126
-
The `confidence` and `salience` values **must** be real numbers between 0 and 1 in the actual output — the `0.0` above is a structural placeholder, not a literal value to echo. Compute them as the maximum across source facts in the group. If you cannot determine confidence or salience, omit the field entirely (the pipeline will fall back to `max(source.*)` from the source records).
126
+
The `confidence` and `salience` values **must** be real numbers between 0 and 1 in the actual output — the `0.0` above is a structural placeholder, not a literal value to echo. Compute them as the maximum across source facts in the group. If you cannot determine confidence or salience, set the field to `null` (the pipeline will fall back to `max(source.*)` from the source records). **Do not omit the keys** — the response schema requires both fields to appear on every group, with either a number or `null` as the value.
127
127
128
128
If a bucket is empty, emit it as an empty array (`[]`) rather than omitting the key.
0 commit comments