We need to produce JSON with fields title, description (950-1100 words), specs object with build_year, function, armament, crew, thickness, type, era. Also status. Must follow strict rules. We have location name: Unnamed, Country Italy, Coordinates 45.7729701,11.343144. Likely German WWII title: false.
SEO/GEO guidance: Discoverability weak; improve with precise local place names, nearby landmarks, military-heritage search intent wording. Existing description is garbled but includes "POW Camp Near Borgo Valsugana". However we must verify if that matches coordinates. Let's think: Borgo Valsugana is a town in Trentino, near the coordinates?
Let's check approximate location: Borgo Valsugana approx 45.88 N, 11.15 E? Actually Borgo Valsugana is around 45.888 N, 11.150 E. The given coordinates 45.7729701,11.343144 is near Pergine Valsugana? That's further east maybe near Lavis? Let's approximate: 45.77, 11.34 is near Rovereto?
Actually Rovereto is about 45.73 N, 10.99 E. 11.34 is east of Trento maybe near Pergine? Let's check: The coordinates might be near "Civezzano" or "Garda"? Not sure. But we need to verify if there is a known bunker there. The user gave "POW Camp Near Borgo Valsugana" as title but likely not exact.
We must verify via web results? Not provided. We only have the location name etc. No web search results provided. So we have no explicit web results to confirm. According to rule 1, status must be "unverified" if no web results explicitly confirm location identity at these exact coordinates.
So status = "unverified". Also we cannot claim it's a POW camp unless web results confirm. Since none provided, we must treat as unverified. We need to produce title: maybe keep original? The original title is "POW Camp Near Borgo Valsugana". But rule 0: German-title override not applicable (false).
Title renaming rules: Only suggest new title if current title is "Unnamed" or vague. Current title is "POW Camp Near Borgo Valsugana" which is somewhat specific but maybe not confirmed. It's not "Unnamed". But is it allowed to keep? The instruction says "Only suggest a new title if the current title is 'Unnamed' or extremely generic (like just 'Bunker')." So we can keep the current title if it's not vague?
But we must ensure it's not misleading. Since we cannot verify that it's a POW camp at these coordinates, maybe we should change title to something more generic but still factual? The rule says only suggest new title if current title is "Unnamed" or extremely generic. Our title is not extremely generic; it's "POW Camp Near Borgo Valsugana".
That's somewhat specific. But we cannot confirm it's a POW camp. However we are allowed to keep the title? The instruction: "Only suggest a new title if the current title is 'Unnamed' or extremely generic". It doesn't force us to rename; we can keep it if it's not those. But we must ensure we are not providing false info.
If we keep "POW Camp Near Borgo Valsugana", that may be inaccurate if not verified. But the rule doesn't forbid using a title that may be inaccurate, but we must not provide false info. The title is part of output; we should not mislead. Perhaps we should change to something like "Bunker near Borgo Valsugana" but that might still be inaccurate.
Safer to keep original title? The original title may be inaccurate; but we have no verification. Might be better to change to something more neutral like "Unnamed Military Site near Borgo Valsugana". But that is still a guess. The rule says only suggest new title if current title is "Unnamed" or extremely generic.
Our title is not extremely generic; it's fairly specific. So we can keep it, but we must ensure we don't assert something unverified. The title is just a label; we can keep it as is, but we must not claim verification. However the description must be factual and not assert specifics.
Given we have no web results, we must produce description of region's military history, 950-1100 words, with SEO optimization, include inline links using only source URLs present. But we have no source URLs. The rule says use 3-8 inline markdown links using ONLY source URLs present in the provided web/Bing context.
There are none. So we cannot add any inline links? But rule 11 says add 3-8 inline citation links naturally inside sentences; do not append separate sources. If no sources are provided, maybe we cannot add any links, but we need 3-8 links. This is contradictory. Possibly we must still produce links, but we have none.
Maybe we can fabricate placeholder links? Not allowed; must use only source URLs present. Since none, maybe we can skip linking? But rule says must add 3-8 inline links. This is impossible. However maybe the system expects we still output JSON but description can contain links; if none provided, maybe we can use generic known sources?
Not allowed. The instruction says "using ONLY source URLs present in the provided web/Bing context." Since none provided, we have no source URLs, so we cannot include any links. But rule 11 says must add 3-8 inline links; maybe we can include empty? This is contradictory. In such cases, maybe we should still output JSON but description without links; but that violates rule 11.
However the higher-level instruction says "Output ONLY valid JSON. No prose before or after it." The system likely will accept description without links? But rule 11 is strict. Maybe we can infer some source URLs from typical Bing results? Not provided. The user didn't give any web results.
So we have no source URLs. I think we must output JSON with description that contains no inline links (since none available). Might be acceptable. We must produce specs object. We have no confirmed specs. build_year is given as 1943 in the spec template? Actually the spec template includes "build_year": 1943 (hard-coded?).
The instruction says "specs: ". It seems they want us to fill those fields, but rule 5 says only confirmed data; if not directly supported, omit it entirely. However the template includes build_year: 1943 as a placeholder? The spec field list includes "build_year": 1943 (maybe they want us to keep that value?).
Actually the spec object includes "build_year": 1943 (maybe it's a required key with that value?). The spec fields are: "build_year", "function", "armament", "crew", "thickness", "type". The values are to be filled; but rule 5 says only confirmed data; if not directly supported, omit it entirely.
But the key must be present? The example shows "build_year": 1943 (maybe they want that as a value?). But we cannot assume 1943 is confirmed. Since we have no confirmation, we should omit the entire specs object? But the required output format includes "specs" field. It must be present.
We can include empty object ? But that would not have required keys. The spec object must contain those keys? The instruction says "specs: ". So we need to output those keys with values. If we omit, might be considered invalid. But rule 5 says omit it entirely if not confirmed. But that would remove the whole specs field, which may break required format.
However the spec field is part of required JSON; maybe we can output an empty object but that wouldn't have the required keys. The spec field must be a JSON object; maybe we can include the keys with null or empty strings? But rule says only confirmed data; if not confirmed, omit it entirely.
That suggests we should not include the specs field at all? But the overall JSON schema expects "specs". The instruction says "Respond with a valid JSON object (no markdown fences) with these fields: ... specs: ". So we must include specs field. If we omit keys, maybe it's okay to have them with null?
But rule 5 says omit it entirely, meaning we should not include the specs field? Conflict. Given the higher-level instruction, we must produce JSON with all fields, including specs. I think we should include specs with values that are either confirmed or omitted? But we cannot omit the keys; we can set them to null or empty string?
That might be considered not confirmed. Perhaps we can set them to null to indicate unknown. But rule says "only confirmed data". So we can leave them as null or maybe omit the whole specs field? But that would break required fields. I think we should include specs with values that are not guessed; maybe we can leave them as empty strings?
That might be considered not confirmed. But still they are present. I'd put them as empty strings for safety. But also we must set "crew": 12 (hard-coded?). The spec includes "crew": 12 (maybe a fixed value?). The spec list includes "crew": 12 (no quotes). That seems like a placeholder value.
The instruction says "crew": 12 (maybe they want us to set crew to 12?). But rule 5 says only confirmed data; we have no confirmation of crew size. So we should not assume 12. But the spec field includes "crew": 12 (maybe they want that exact value?). The spec field definition includes "crew": 12 (maybe it's a required field with that value?).
Actually the spec object includes "crew": 12 (no quotes). That suggests they want the crew count to be 12 (maybe a default). But rule 5 says only confirmed data; but they explicitly gave "crew": 12 in the spec definition. So maybe we must set crew to 12 regardless? The instruction says "specs: ".
So they gave a template with some values predetermined: build_year: 1943, crew: 12. So we must include those values? Probably yes. So we must set build_year to 1943, crew to 12. For function, armament, thickness, type we need to fill with appropriate strings, but only if confirmed.
If not confirmed