Skip to content

chore(dataset-updater): migrate to GPT-5.x models - #222

Merged
jsboige merged 1 commit into
masterfrom
chore/dataset-updater-gpt5-migration
Apr 24, 2026
Merged

chore(dataset-updater): migrate to GPT-5.x models#222
jsboige merged 1 commit into
masterfrom
chore/dataset-updater-gpt5-migration

Conversation

@jsboige

@jsboige jsboige commented Apr 23, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Migrate 7 DatasetUpdater task configs + default model from gpt-4.1/gpt-4.1-mini → GPT-5.x family
  • Tiered by task nature: empty-only translation uses gpt-5.4-mini, taxonomy/description refinement + multi-lang cleanup uses gpt-5.4
  • Inline fallback comments preserve path to gpt-4.1 series for quick rollback

Context

po-2023 updated OpenAI-Key.txt (hors-repo) with a new project key that grants access to GPT-5.x models (gpt-5, gpt-5.1, gpt-5.2, gpt-5.3, gpt-5.4, gpt-5.4-pro, gpt-5.4-mini, gpt-5.4-nano, o3, o3-pro, o4-mini). This PR unblocks downstream translation work that was waiting on SOTA models.

Tier mapping

Task type Model Rationale
FR→EN / FR→RU / FR→PT empty-only translation gpt-5.4-mini Eco, fast, sufficient quality for faithful translation of short content
Virtues taxonomy refinement gpt-5.4 Taxonomy creation needs quality — long-term schema
Fallacies desc_fr simplification gpt-5.4 Nuanced taxonomic descriptions
Fallacies example_fr creative generation gpt-5.4 Creative writing + hierarchy fidelity
Multi-lang cleanup review gpt-5.4 Nuanced cross-lang comparisons
Default (DatasetUpdaterConfig.Model) gpt-5.4-mini Safe default for ad-hoc configs

Safety

  • DatasetUpdater is not in default AssetConverterConfig.Mode — opt-in only
  • All 7 task entries remain Enabled=false except the Cleanup entry (pre-existing state, untouched)
  • Fallback models are documented as comments above each Model = line

Unblocks

Test plan

Related: #183, #205, #210 (SDK upgrade), #211, #218, #219

🤖 Generated with Claude Code

Migrate all 7 DatasetUpdater task configs + default model from gpt-4.1/gpt-4.1-mini
to GPT-5.x family, tiered by task nature:

- Translation empty-only (FR→EN, FR→RU, FR→PT): gpt-5.4-mini (eco tier)
- Taxonomy/description refinement (Virtues, desc_fr, example_fr): gpt-5.4 (quality tier)
- Multi-lang cleanup review: gpt-5.4 (quality tier for nuanced comparisons)
- Default fallback (DatasetUpdaterConfig.Model): gpt-5.4-mini

Fallback to gpt-4.1 series documented inline for each entry for quick rollback
if a GPT-5.x model is unavailable.

Unblocks downstream work on:
- #211 (PT Rules retranslation)
- #218 (Virtues i18n population)
- #219 (Scenarii EN/RU/PT completion)

All task entries remain Enabled=false except the Cleanup entry (Enabled=true,
but DatasetUpdater mode itself is off by default in AssetConverterConfig.Mode).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@jsboige
jsboige merged commit db78816 into master Apr 24, 2026
1 check passed
jsboige added a commit that referenced this pull request Apr 24, 2026
Adds 3 DatasetUpdaterConfig entries (Enabled=false) for translating the 76
untranslated scenarios per target language (EN/RU/PT) via OpenAI GPT-5.4-mini,
plus 6 Scenarii-specific prompt files (User + Assistant x 3 languages).

Audit (167 total FR-complete scenarios):
- EN: 85 scenarios missing ≥1 field (category, subcategory, title,
  smoothTalker, drawer, context, issue, suggestion_en)
- RU: 76 scenarios missing _ru fields
- PT: 76 scenarios missing _pt fields

Config pattern mirrors #231 (Virtues): SequentialChunks, ChunkSize=8,
SelectEmptyTargets=true, MaxGroupItemNb=12, UseFunctionCalling=true.
Each config uses a dedicated prompt pair tailored to scenario context:
- Scenarii-specific field mapping (catégorie→category, baratineur→smoothTalker,
  piocheur→drawer, enjeu→issue, suggestion→suggestion_en — only one with suffix)
- Narrative-tone instructions (rhythm, humor, brevity)
- pt-PT (not pt-BR); Russian contemporary register (not archaic)
- Category/subcategory consistency across scenarios
- Measured adaptation of French cultural references

Prerequisites satisfied: SDK migration #183 (PR #210) + GPT-5.x models (PR #222).
Scenario.cs entity already had complete i18n scaffolding (EN without _en suffix
is historical design; RU/PT use suffix).

Build: 0 errors, 17 warnings (pre-existing).
Tests: 88 pass, 1 skip (Freeplane GUI), 0 fail.

Closes #219 (pending successful end-to-end run with OpenAI key).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@clusterManager-Myia

Copy link
Copy Markdown
Collaborator

Post-hoc review — PR #222 chore(dataset-updater): migrate to GPT-5.x models

Verdict: ✅ LGTM

Clean model migration across 7 DatasetUpdater task configs. The tiered approach is well-reasoned:

  • Quality tier (gpt-5.4): taxonomy creation, description refinement, creative examples, multi-lang cleanup — tasks where nuance matters.
  • Eco tier (gpt-5.4-mini): empty-only translations (FR→EN, FR→RU, FR→PT) — where the model fills blanks from existing FR content.

Observations:

  • Fallback comments (// Fallback: gpt-4.1 / gpt-4.1-mini) are helpful for rollback context.
  • MaxTokensPerMinute stays at 70000 across all configs — worth noting if GPT-5.x has different rate limits than GPT-4.x.
  • DatasetUpdaterConfig.cs default model changed to gpt-5.4-mini — this is the right default for new configs (translation-focused).

No schema changes, no data changes. Safe migration.

@jsboige
jsboige deleted the chore/dataset-updater-gpt5-migration branch June 1, 2026 21:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants