data(cpu): add 15 Intel Core parts the dataset was missing - #160
Conversation
Wikipedia's Intel Core desktop and mobile lists document these; we had no record of them. Every required field is read from the source row or the page it sits on — manufacturer and segment from the page, core and thread counts from its "Cores (Threads)" column, clocks, cache and TDP from the row. The day of month is the one thing the tables do not state, so a month-precise date is written as the 1st rather than inventing a day. Rows whose date cell did not parse as a date were dropped, not guessed at: one of them held "US $384". Two classes of row are deliberately excluded because their core counts cannot be trusted: * Hybrid generations (Alder Lake onward) split P-cores and E-cores into separate rowspan'd columns; the single figure picked up for such a part is the P-core count. It read the i9-13900T as 8c/16t when the part is 24c/32t. * Rows whose core count is inherited from a rowspan that crosses a brand tier — an i7's cell reaching an i5. That is how the i5-10310Y (2c/4t) picks up the i7-10510Y's "4 (8)". Within one tier the grouping is the table's normal shorthand and is kept. Refs #1
🔎 Data verification — Tier 0 (offline existence/trust)Scored by Changed records in this PR15 record(s) scored. %%{init: {"theme":"base","themeVariables":{"pie1":"#3fb950","pie2":"#d29922","pie3":"#f85149","pieStrokeWidth":"0px","pieOpacity":"1"}}}%%
pie showData
title Verification bands — all records
"Green" : 15
"Yellow" : 0
"Red" : 0
Full-dataset baseline105757 record(s) scored. %%{init: {"theme":"base","themeVariables":{"pie1":"#3fb950","pie2":"#d29922","pie3":"#f85149","pieStrokeWidth":"0px","pieOpacity":"1"}}}%%
pie showData
title Verification bands — all records
"Green" : 21328
"Yellow" : 83228
"Red" : 1201
Hard violations (forced red):
green = authoritative source + complete + consistent · yellow = plausible, needs confirmation · red = sparse/weak source or a hard contradiction. Promotion to |
TechEngine change review: PASS
Changed data
Changed record examplescpu added
Heuristic review
|
TechEngine validation stats: PASS
Data summary
Warning Tracked verified coverage is below 50% for watch 4.2% (18/433), tablet 6.3% (218/3455), soc 6.9% (146/2104), brand 11.6% (24/207), smartphone 18.6% (17384/93396), all 20.2% (21314/105757), gpu 39.9% (809/2030), pda 47.1% (66/140). Validation notes
Key output:
|
15 Intel Core parts that Wikipedia's desktop and mobile lists document and this dataset had no record of — the first net-new hardware records in a while, each carrying a Tier-1 source.
Every required field comes from the source: manufacturer and segment from the page, cores and threads from its
Cores (Threads)column, clocks / cache / TDP / process node from the row. The day of month is the only thing the tables do not state, so a month-precise date is written as the 1st rather than inventing a day.What was deliberately thrown away
The candidate pool started at 400 and finished at 15. Each cut removed a class of wrong record, not a class of inconvenient one:
Phenom X4 9100evs ouramd-phenom-9100e-quad-core— same chip)Cores (Threads)cell, or a date cell that isn't a date (one heldUS $384)4 (8). Inheritance within one tier is the table's normal shorthand and is keptAll 15 were checked against the real parts.
Dump
Regenerated for
cpusat the pinned engine (d84bcec); collection count 3,977 → 3,992 so the manifest entry updates.The diff is larger than 15 records because the published dump's
verifiedflags were stale: promotion PRs flipverifiedindata/but never refreshsite/public/v1, so 3,326 CPU pages were still advertising the old value. This refresh brings them in line. That gap is worth closing properly — promotions should either refresh the affected pages or the site should readverifiedfrom the ledger.python -m app.validatepasses.Closes #1