ASortie produite
VARIANTE A
Des en-têtes th + scope
Ligne de valeurs attendue : Valeurs exactes, dans l’ordre · En-têtes de colonnes : En-tête Markdown · En-tête de ligne : Non encodé en Markdown. Source
01 · Le HTML qui change
<table><caption>Synthetic measurements</caption><thead><tr><th class="case-cell" scope="col">Indicator</th><th class="case-cell" scope="col">Unit</th><th class="case-cell" scope="col">Period</th><th class="case-cell" scope="col">Value</th></tr></thead><tbody><tr><th class="case-cell" scope="row">Response time</th><td class="case-cell">seconds</td><td class="case-cell">May 2026</td><td class="case-cell">1.8</td></tr></tbody></table>Extrait exact de l’entrée · HTML original ↓
02 · Ce que l’outil produit MARKDOWN
…
client.
## Synthetic measurements
Synthetic measurements
| Indicator | Unit | Period | Value |
| --- | --- | --- | --- |
| Response time | seconds | May 2026 | 1.8 |
The conclusion must be read with its unit, period, scope and caveat. Finding a word in an output is not enough to prove that the relationship was preserved.
Offline synthetic fixture · v1.2.0Extrait repéré par l’évaluateur corrigé. Sortie complète ci-dessous.
03 · L’observation documentée
- Ligne de valeurs attendue
- Valeurs exactes, dans l’ordre
- En-têtes de colonnes
- En-tête Markdown
- En-tête de ligne
- Non encodé en Markdown
- Structure de la sortie
- Disposition Markdown
Source des verdicts : results.json · table-en-1 / markdownify
Examiner la preuve complète
Les verdicts ci-dessus proviennent de results.json corrigé. Les champs evaluation du fichier brut sont historiques et ne font pas autorité ici.
results.json/cases/8/evaluation/relation/markdownify
Verdict corrigé, sans modification
{
"status": "ok",
"tool_class": "markdown_converter",
"format": "markdown",
"table_structure": "markdown_layout",
"expected_data_row": "exact_values_in_order",
"column_header_relation": "markdown_header_row",
"row_header_relation": "not_encoded_in_markdown",
"column_labels": [
"Indicator",
"Unit",
"Period",
"Value"
],
"data_values": [
"Response time",
"seconds",
"May 2026",
"1.8"
],
"evidence": {
"header_row": "| Indicator | Unit | Period | Value |\n| --- | --- | --- | --- |",
"data_row": "| Response time | seconds | May 2026 | 1.8 |",
"table_excerpt": "| Indicator | Unit | Period | Value |\n| --- | --- | --- | --- |\n| Response time | seconds | May 2026 | 1.8 |"
},
"output_field": "additional_extractors.markdownify.markdown",
"output_sha256": "b89ed68e1940ec52ddc6c2ca9f80ec35d1b57d7cde93df26244dd029a4fcff13",
"source_column_headers_explicit": true
}Sortie complète du champ étudié
additional_extractors.markdownify.markdown
Offline protocol for preserving relationships
Edikka · semantic HTML extraction protocol · v1.2.0
# Offline protocol for preserving relationships
This synthetic document compares two markups while text, order, classes and surroundings remain identical. The data are fictional and describe neither Edikka nor a client.
## Synthetic measurements
Synthetic measurements
| Indicator | Unit | Period | Value |
| --- | --- | --- | --- |
| Response time | seconds | May 2026 | 1.8 |
The conclusion must be read with its unit, period, scope and caveat. Finding a word in an output is not enough to prove that the relationship was preserved.
Offline synthetic fixture · v1.2.0Version et options archivées
markdownify 1.2.2 · Exécution 2026-09-20
{
"version": "1.2.2",
"configuration": "Aucun champ configuration dans cette sortie ; consulter le runner archivé."
}Runner archivé · Options Python
Empreintes SHA-256
- Entrée HTML
374211644b0d1ad2d4ae9647d84e7e3e518ff392b9f4aaa108e438677c2b05da- Champ de sortie évalué
b89ed68e1940ec52ddc6c2ca9f80ec35d1b57d7cde93df26244dd029a4fcff13