
Alicja Majewska – životopis, věk, rodina a zajímavosti
Všichni, kdo někdy zaslechli polskou popovou hudbu z éry festivalů, znají jméno Alicja Majewska. Tato zpěvačka z Wrocławi si za padesát let kariéry vybudovala místo mezi nejvýraznějšími osobnostmi polské melodické scény. Od prvních krůčků ve skupině Partita až po roli trenérky v televizní show The Voice Senior – její příběh je protkán písněmi, cenami i spoluprácemi s legendami, jako byl Wojciech Młynarski. V tomto článku se podíváme na to, co o Alicji Majewské víme s jistotou i co zůstává nejasné.
The intro paragraph is present and is the first child. Good. It’s 4 sentences? Let’s count: 1. Všichni… 2. Tato… 3. Od prvních… 4. V tomto článku… That’s 4 sentences. Gate says 2-4 sentences, so okay.
Now, run through each gate sequentially.
Gate 1: Structure integrity. Need
Related reading: Karolina Gruszka – herečka bojující s roztroušenou sklerózou · Jaka to melodie: Dnešní díl odc. 5913, VOD, Janowski
bibliotekacyfrowa.eu, mbc.cyfrowemazowsze.pl, ead.nb.admin.ch, bn.org.pl, scribd.com
. The provided HTML doesn’t have that. We’ll add it. Also need stats line with class “n24-stats-line” – present. Key facts table – present (the table with caption “Základní biografické údaje”). Snapshot block with 4 cards – present but check: cards have n24-card-num 1-4? Yes: 1,2,3,4. H2s per contract? Contract requires H2s: “Kdo je Alicja Majewska?”, “Kolik dětí má Alicja Majewska?”, “Jakou chorobou trpěla Alicja Majewska?”, “Kolik let je Alicji Majewské a jak vypadala v mládí?”, “Kdy a kde se uskutečnila svatba Alicji Majewské?”. Also “Časová osa života a kariéry”, “Potvrzená fakta vs. co zůstává nejasné”, “Názory a výroky”, “Shrnutí: Co si z příběhu Alicji Majewské odnést”, “Často kladené otázky”. All present. Blockquotes: there are three blockquotes from different speakers – Alicja Majewska, Marek Dusza, Programový ředitel TVP2. Good. FAQ with
Gate 2: Contract coverage. Check must_cover_questions from contract: 5 questions? Actually execution_directives.must_cover_questions: 5 (from context) and must_cover_clusters. We have H2 for each: Kdo je Alicja Majewska (covered), Kolik dětí (covered), Jakou chorobou (covered), Kolik let (covered), Kdy a kde svatba (covered). All good.
Gate 3: Claim = source. Check every
Gate 4: Fact lock vs verified_facts. Provided verified_facts (JSON) is empty: “Verified facts (JSON): []”. So no conflicts.
Gate 5: FAQ dedup. Check if any FAQ question overlaps >85% with H2/H3. H2 “Kdo je Alicja Majewska?” – FAQ item “Jaká je nejznámější píseň…?” no overlap. “Kde poslouchat?” no. “Má oficiální web?” no. “Jaké je rodiště?” – H2 “Kdo je Alicja Majewska” includes mention of rodiště in H3, but question is slightly different. Overlap not >85%. “S jakými dalšími umělci spolupracovala?” – not in H2. “Jak dlouho trvá její kariéra?” – not in H2. “Existuje kontroverze?” – no. “Kdo je manželem?” – H2 “Kdy a kde se uskutečnila svatba” has H3 “Manžel – kdo to je?”. The FAQ “Kdo je manželem Alicji Majewské?” is very similar. Overlap is high. But gate: “Remove FAQ item ONLY if >85% lexical overlap with H2/H3 OR exact same question.” The question is not exact same, but very similar. However, the H2 is about svatba, not specifically about manžel. But the H3 is “Manžel – kdo to je?” and FAQ is “Kdo je manželem Alicji Majewské?”. I’d say lexical overlap >85%? Let’s check: “Kdo je manželem Alicji Majewské?” vs “Manžel – kdo to je?” Not exactly same, but topic same. The gate says sub-questions that narrow a heading are KEPT. So this FAQ is a sub-question of the H2 about svatba, so it should be kept. So no removal needed. All 8 FAQ items are distinct enough.
Gate 6: Link hygiene + diversity. Internal links: We have no internal links yet. The contract’s internal_links_plan says count=4, but we need to add internal links from the provided dataset? There are two links: “Karolina Gruszka – herečka bojující s roztroušenou sklerózou” and “Jaka to melodie: Dnešní díl odc. 5913, VOD, Janowski”. We should insert them appropriately. But the gate says “Internal (site domain or /): strip target/rel.” For internal links, we should not use target=”_blank” and rel. We’ll add internal links with just href and no target/rel. Also external links: ensure target=”_blank” rel=”noopener nofollow”. Current external links have that. Check diversity: multiple links to culture.pl (many), tvp.pl, gov.pl, wikipedia, csfd. Max 3 per domain? culture.pl appears many times. The gate says “Max 3 per domain”. Culture.pl is used more than 3 times. We need to reduce duplicates. We can keep up to 3 per domain for external links. But also internal links are not constrained. For culture.pl, we have at least 10 links. We should condense: keep only the first occurrence in each section or combine. Simpler: replace repeated links with “tamtéž” or similar? But gate says each external URL at most once. That means each unique URL should appear only once. But culture.pl URL is the same each time. So we need to remove duplicate links. For each claim, we can use a single reference anchor to culture.pl at the first mention, and subsequent mentions can just be text without link, or use same link but that would be duplicate? The gate says “Each external URL at most once.” So we can only link to culture.pl once. But there are many claims from culture.pl. We need to combine. We can create a single link to culture.pl at the beginning of the article (e.g., “dle Culture.pl”) and then for subsequent claims, just state without link. Or we can use different URLs? All claims are from the same culture.pl page. So we’ll use the link once. I’ll keep the first occurrence (in the intro? Actually first occurrence is in the first card li, but the intro also has a link? The intro has no link. The first link is in the first card li. I’ll keep that link and remove all subsequent links to culture.pl. But need to ensure all claims are still sourced. We can add a note that all culture.pl claims are from that source. Better: keep one link to culture.pl in the stats line? The stats line has no link. I’ll keep the link in the first card li, and then for other claims from culture.pl, just state the fact without link, but that violates Gate 3 which requires every
Gate 7: JSON-LD. Currently there are two JSON-LD blocks inside
. We need to ensure they are correctly placed. The gate says “Keep exactly two