We need to produce JSON with fields title, description, specs, status. Must obey rules. Given location: Unnamed, Country Poland, coordinates 50.0380734,20.1202648. Likely German WWII title false. SEO/GEO guidance: discoverability weak, improve findability naturally with precise local place names, nearby landmarks, military-heritage search intent wording.
Existing description is garbled, mentions Cold War Nuclear Bunker near Kraków. But we must verify if that matches coordinates? Let's think: coordinates 50.0380734,20.1202648 are near Kraków? Kraków is approx 50.064138,19.945907. The given coordinates are close to Kraków, but slightly west.
Could be near the village of Wieliczka? Actually Wieliczka is ~50.066,20.03. The coordinates are near the area of "Nowa Huta"? That's part of Kraków. Could be near "Kraków" region. But we need to verify if there is a known bunker at those coordinates. We have no web results provided.
The user gave no web search results. So we have no source URLs to link. We must be careful: we cannot fabricate sources. We can only use provided web results, but there are none. So we must treat as unverified? According to rule 1: status must be "verified" only if web results explicitly confirm location exists and match coordinates/country.
Since no web results, we cannot verify. So status should be "unverified". Also we cannot claim it's a Cold War Nuclear Bunker unless web results confirm. So we must not assert that. We must produce a description that is long (950-1100 words) describing the region's military history, but must be based on web results.
Since none, we can describe Poland's military history in Cold War, but must mark uncertain specifics as "unconfirmed" or "possibly". However rule says: "If no web results and nothing can be reliably inferred: still produce 950-1100 words by describing the country's general WWII/Cold War military history context and clearly mark uncertain specifics as "unconfirmed" or "possibly"." So we can do that, but must be careful to not present speculation as fact.
Must embed inline source links using only URLs present in provided web/Bing context. There are none. So we cannot add any inline links? But rule 11: Inline source links required. Use 3-8 inline markdown links in the description (for places, operations, organizations, technical terms) using ONLY source URLs present in the provided web/Bing context.
Since none, we cannot add any links. But we must still produce 3-8 inline links? The rule says required, but if no sources, perhaps we cannot satisfy. However we could still produce description without links? The rule says "required". But we have no sources, so we cannot include any.
Might be acceptable to have zero links? But rule says 3-8 inline source links required. If we cannot, maybe we need to fabricate? Not allowed. We must only use source URLs present. Since none, we cannot include any. This is a conflict. Possibly we can still produce description without links, but that violates rule.
However maybe we can use generic placeholder URLs? Not allowed. Must use only source URLs present. So we have none, so we cannot include any links. Might be okay to have zero? The rule says required, but maybe we can still produce description and not include links; but that would be violating.
However the system may not enforce strictly if no sources exist. I think we can produce description without inline links, but we must not add any links that are not from sources. So we will output description with no markdown links. We also need to output specs field with build_year, function, armament, crew, thickness, type, era.
These must be based on confirmed data. Since we have no confirmed data, we cannot fill them. The spec fields are required? The JSON schema includes them. We must provide values. If not confirmed, maybe we can leave them as null? But schema expects certain types: build_year number, function string, armament string, crew number, thickness string, type string (must be one of allowed).
If we cannot confirm, perhaps we can omit? But they are required fields. We must provide something. Could we set them to null? That would break type. Could we set them to empty strings? For numeric fields, maybe 0? But that would be inaccurate. However rule 5: Specs: only confirmed data.
If a spec field is not directly supported by the web results or the location name/type, omit it entirely. So we can omit them entirely? But the JSON schema includes them; maybe we can leave them out? The instruction says "Respond with a valid JSON object (no markdown fences) with these fields".
So we must include them. But rule 5 says omit if not confirmed. Conflict. I think we can include them with null or empty? But that may not be "omit". Perhaps we can set them to null and still be valid JSON. But spec type expects number/string. Null is not number or string. Might be considered invalid.
Better to provide placeholder values that are not claimed as factual? Could we set them to 0 or empty string? That might be considered a value but not accurate. However rule 5 says omit it entirely, but the output must have the field. Maybe we can set them to null and still be considered omitted?
Not sure. Given the constraints, perhaps we can set them to null and hope it's acceptable. But maybe we can set them to 0 for numeric, "" for strings, and "Other" for type? But that would be a guess. Not allowed. Maybe we can set them to the values from the existing description: build_year 1943?
That is not confirmed. The existing description mentions "Cold War Nuclear Bunker near Kraków". But we cannot assume build_year 1943. Actually spec field "build_year" is required but we have no confirmed data. Could we set it to 0 to indicate unknown? That might be considered a value but not a guess.
Might be okay. But rule 0: German-title override not applicable. We need to decide title. Current title is "Cold War Nuclear Bunker near Kraków". Is that a good title? It is somewhat specific but not confirmed. The rule for title renaming: only suggest new title if current title is "Unnamed" or vague.
The current title is not "Unnamed"; it's "Cold War Nuclear Bunker near Kraków". It's somewhat specific but maybe not confirmed. The rule says only suggest a new title if current title is "Unnamed" or extremely generic (like just "Bunker"). This title is not extremely generic; it's more specific.
So we should keep it as is, unless we can confirm it's wrong. But we must ensure title is 2-5 words, factual, confirmed by web results. Since we have no confirmation, we cannot claim it's a "Cold War Nuclear Bunker near Kraków". That might be inaccurate. But the rule doesn't require that the title be verified; it just says only suggest new title if current is generic.
It doesn't require verification of title content. However rule 1 about status verification is separate. The title can be kept as is. But we must ensure title is short (2-5 words). "Cold War Nuclear Bunker near Kraków" is 5 words? Actually count: Cold(1) War(2) Nuclear(3) Bunker(4) near(5) Kraków(6) => 6 words.
That's too many. Title must be 2-5 words. So we need to rename it to something 2-5 words, factual, confirmed. Since we cannot confirm, maybe we can use "Bunker near Kraków" (3 words). That is shorter. But is that factual? It's near Kraków, but we don't know if it's a bunker. But we can keep it as title?
The rule says only suggest new title if current is "Unnamed" or extremely generic. Our current title is not extremely generic, but it's longer than allowed (must be 2-5 words). The rule didn't specify length constraint for existing title, but the new title must be 2-5 words. We can keep the current title if it meets length?
It doesn't. So we might need to rename it to a shorter title that is still factual. Could we use "Kraków-area Cold War Bunker"? That's 4 words? Actually "Kraków-area Cold War Bunker" = 4 words? Count: Kraków-area(1) Cold(2) War(3) Bunker(4). That's 4 words, but includes hyphen maybe considered one?
Probably okay. But is it confirmed? Not really. Maybe we can set title to "Polish Cold War Bunker". That's 3 words, but not specific to location. Might be okay. But we must ensure it's factual and confirmed by web results. Since no results, we cannot confirm any specific name. So maybe we should leave title unchanged?
But length constraint not enforced for existing title? The rule says "The new title MUST be 2-5 words, factual, and CONFIRMED by web search results to be at these coordinates." That's for when we suggest a new title. We are not required to suggest a new title unless current is "Unnamed" or extremely generic.
Our current title is not extremely generic, but it's longer than 5 words. The rule doesn't say we must enforce length on existing title. It only says if we suggest a new title, it must be 2-5 words. So we could keep the current title as is, even though it's 6 words, because we are not suggesting a new title.
The rule doesn't forbid keeping a longer title. So we can keep "Cold War Nuclear Bunker near Kraków". That is the current title. It's not "Unnamed". So we keep it. Now description must be 950-1100 words, encyclopedic, third-person, include inline source links (but none). Must be long.
Must cover historical background, strategic role, architecture/engineering, geographic setting, present condition, heritage/visitor relevance. Must be based on web results; we have none, so we must describe region's military history generally, marking uncertain specifics as "unconfirmed" or "possibly". Must be 950-1100 words, which is a lot.
Must be English. We must also incorporate SEO/GEO guidance: improve findability naturally with precise local place names, nearby landmarks, and military-heritage search intent wording. So we should mention "Kraków", "Lesser Poland Voivodeship", "Vistula River", "Wawel Castle", "Nowa Huta", "Tyniec Abbey", "Kraków Old Town", "Kraków's WWII history", "Cold War era in Poland", "Polish Armed Forces", etc.
We must not mention internal labels. Must not mention "unverified" in description? The status