We need to produce JSON with fields: title, description, specs, status. Title may need renaming if appropriate. We have location name Unnamed, country United States, coordinates 33.6387736,-85.9735351. Likely German WWII false. SEO/GEO guidance: Discoverability weak; need to improve findability naturally with precise local place names, nearby landmarks, and military-heritage search intent wording.
We have existing description: basically says near Fort Benning, Alabama, US, but not confirmed. We need to write a description of 950-1100 words, blog style, third-person, encyclopedic, with inline markdown links (3-8) using only source URLs present in provided web/Bing context. However we have no web search results provided in the prompt.
The user only gave location name, country, coordinates, and guidance. No web results. So we have no source URLs to link to. But rule says we must include inline source links using ONLY source URLs present in the provided web/Bing context. Since none provided, we cannot add any links?
Possibly we can still include none? But requirement: "Add inline citation links naturally inside sentences; do not append a separate 'Sources' section." It also says 3-8 inline markdown links required. If we have no source URLs, we cannot satisfy that. However maybe we can infer some typical sources?
But rule says only use URLs present in provided web/Bing context. Since none provided, we have none. Could we still output JSON without links? That would violate requirement of 3-8 inline source links. But maybe we can still produce description without links, but that would break rule.
However maybe we can still produce description with placeholder links? Not allowed. Must be valid JSON with description field containing text that may include markdown links. If we have no URLs, we cannot include any links, which would violate the requirement of 3-8 inline source links.
But maybe we can still produce description that doesn't include any links, but that would not meet the "Add inline citation links naturally inside sentences; do not append a separate 'Sources' section." It doesn't explicitly say you must have 3-8 links; it says "Add inline citation links naturally inside sentences; do not append a separate 'Sources' section." It also says "3-8 inline markdown links required." So we need to include 3-8 links.
Since we have no source URLs, perhaps we can use generic URLs? Not allowed; only source URLs present in provided web/Bing context. There are none. Could we maybe use the same URL for multiple links? But we need actual URLs. Maybe we can use the location's Wikipedia page? But that might not be present in provided context.
Not allowed. Potential approach: Since no web results are given, maybe we can treat that as "no web results" and thus we cannot verify location, so status = "unverified". Title maybe remains "Unnamed" or we can rename to something like "Bunker near Fort Benning". But rule: Title rename only if current title is "Unnamed" or vague, and we can propose a new title if we have confirmation.
We have no confirmation of a specific name. However we can use fallback: "Bunker near Fort Benning, Alabama". That is 5 words? Actually "Bunker near Fort Benning, Alabama" is 5 words? Count: Bunker(1) near(2) Fort(3) Benning,(4) Alabama(5). That's 5 words, okay. But we need to ensure it's confirmed by web results.
We have no web results, but the existing description mentions "near Fort Benning, Alabama". However we cannot confirm that this specific coordinate corresponds to that. The existing description says "A military bunker located near Fort Benning, Alabama, United States. The specific historical context... are not confirmed".
So we cannot claim it's near Fort Benning as a confirmed fact; it's just speculation. So we cannot rename title to that because we cannot verify. So title remains "Unnamed". Maybe we can keep it as "Unnamed". That's acceptable. Now specs: we need to fill specs fields. build_year is given as 1943?
Actually spec says "build_year": 1943 (maybe a placeholder?). The spec field build_year is predetermined? The spec JSON includes "build_year": 1943. That seems fixed? The spec definition shows "build_year": 1943, but that seems like a placeholder value? Actually spec field is defined as "build_year": 1943, but that might be a required field with that value?
The spec says "build_year": 1943, but that seems like a sample? The instruction: "specs: ". It seems they want us to fill those fields, but build_year is set to 1943? Or is that just an example? The spec likely expects us to put the actual build year if known; but they gave 1943 as a value?
Might be a default placeholder. 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. Do not guess build years, crew sizes, or armament." So we should omit any spec fields that are not confirmed.
But the spec JSON includes those fields; we must output them. But we can maybe set them to null? Or we can leave them out? The instruction says "specs: ". Probably we need to include all those keys, but we can set values to something appropriate or maybe empty string? But they said "omit it entirely" if not confirmed.
That suggests we should not include that key? But the spec structure includes them; maybe we need to include only those that are confirmed, but the JSON schema expects those keys? The instruction: "specs: ". It seems they gave example values, but we need to fill them with actual data.
If not confirmed, we should omit the key? But the spec includes them; maybe we should set them to null or empty string? However "omit it entirely" suggests we should not include that key at all. But then the JSON would be missing required keys? The spec is part of output format; maybe they expect all keys but can be any value?
The rule says "If a spec field is not directly supported by the web results or the location name/type, omit it entirely." So we can simply not include that key in the JSON? But then the output would be missing that key, which might break the expected structure. However they said "omit it entirely", meaning we should not include that field in the JSON.
So we can output only the fields we have? But the top-level JSON must have "specs" object; maybe we can have an empty object "specs": ? That would omit all spec fields. That might be acceptable. But they also gave "crew": 12 as a value; maybe that is a default? But rule says do not guess crew sizes.
So we cannot set crew to 12 unless confirmed. So we should omit crew field. Similarly for build_year, function, armament, thickness. So we can output "specs": . But maybe they expect at least some fields? The spec includes "type" which must be one of allowed values. We can determine type based on verification.
Since we cannot confirm it's a specific type, maybe it's "Other"? The allowed list includes "Other". So we can set type to "Other". That is a confirmed value? Not exactly; it's a fallback. But we can set it because it's allowed. The rule says "type: string (MUST BE exactly one of: ... )".
So we need to set it to one of those. We can choose "Other" if none apply. That is allowed. So we can include "type": "Other". Similarly "era": maybe "Cold War" or "Unspecified"? But we need a string; we can set "era": "Unknown"? Not in allowed list; but era is not restricted to that list; only type is restricted.
So we can set era to something like "20th century" maybe. But we need to base on web results; we have none. Could set "era": "20th century" but that's not a specific era like WWII, Cold War. Might be okay. But maybe better to set "era": "Unknown". That's a string. It's not restricted.
So we can include. But rule 5: only confirmed data; if not confirmed, omit. So "era" maybe we can omit? But it's part of spec; maybe we can include "era": "Unconfirmed". That is a string but not a known era; but it's still a string. Might be okay. But maybe better to omit if not confirmed.
However they didn't say to omit era; only said "If a spec field is not directly supported by the web results or the location name/type, omit it entirely." So we could omit era as well. But then we would have no era field. That might be okay. But the spec JSON example includes era field; maybe they expect it.
I'd include "era": "Unconfirmed". That is a string, not a specific era, but it's okay. Now status: we need to set status to "verified" only if web results explicitly confirm location exists and match coordinates/country. We have no web results, so we cannot confirm. So status = "unverified".
Now description: Must be 950-1100 words, English, third-person encyclopedic tone, with inline markdown links (3-8) using only source URLs present in provided web/Bing context. Since none provided, we cannot include any links, which violates requirement. However maybe we can still include links to generic sources that are not provided?
The rule is strict: "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 there are none, we cannot add any links. That would break the requirement. But maybe we can still produce description without links, but then we would not meet the "3-8 inline markdown links required".
The instruction says "Add inline citation links naturally inside sentences; do not append a separate 'Sources' section." It also says "3-8 inline markdown links required." So we must include at least 3 links. Since we have no URLs, maybe we can fabricate placeholder URLs? Not allowed.
Must use only source URLs present in provided web/Bing context. There are none. So maybe