Corpus Engine Towards a reproducible .science file.
← All .science files

pmid:39647324

Development and validation of a prognostic and drug sensitivity model for gastric cancer utilizing telomere-related genes.

Translational oncology · 2025 doi:10.1016/j.tranon.2024.102232

Paper

partial

Experiment

partial

Data

partial

Analysis

absent

Execution

absent

Execution evidence has not yet been added to this .science file. Explore its methods, data and open questions to plan the next step.
Record details sci_version · id · kind · revision · content_hash · schema · created_at · updated_at · generator
id
pmid:39647324
kind
science-record
content_hash
sha256:738267c06f6fd64896e5967f98df6a5a9db39fafade781e92a458277bc3edfe4
schema
https://corpus.bntrg.co.uk/sci/1.0/sci.schema.json
created_at
2026-11-01T10:25:48Z
updated_at
2026-11-01T14:01:32Z
generator object · 3 fields
name
corpus-assay-engine
converter
sep_to_sci_v1
source_package_schema
urn:bntrg:sep:1.0.0
paper object · 10 fields
state
partial
title
Development and validation of a prognostic and drug sensitivity model for gastric cancer utilizing telomere-related genes.
doi
10.1016/j.tranon.2024.102232
pmid
39647324
authors
null
journal
Translational oncology
year
2025
abstract
null
claims array · 1 item
[0] object · 6 fields
id
claim-1
statement
the headline numerical result the paper states for its main finding
kind
qualitative
state
blocked
target object · 4 fields
value
null
unit
null
tolerance
null
source
null
evidence array · 0 items
gaps array · 2 items
[0]
abstract
[1]
authors
experiment object · 8 fields
state
partial
objective
the headline numerical result the paper states for its main finding
steps array · 3 items
[0] object · 13 fields
id
read_published_estimate
order
1
name
Read the published estimate and its interval from the source
kind
other
state
complete
blocked_on
null
description
The number a replication must land on, and the sentence it came from.
parameters object · 0 fields
inputs array · 1 item
[0]
source:pmid:39647324
outputs array · 1 item
[0]
the published estimate, its unit and its interval
instruments array · 0 items
reagents array · 0 items
[1] object · 13 fields
id
obtain_source_data
order
2
name
Obtain the source data behind the published result
kind
data-preparation
state
blocked
blocked_on
data:not_downloaded
description
The published result cannot be recomputed without the data the paper analysed.
parameters object · 0 fields
inputs array · 0 items
outputs array · 1 item
[0]
the source data with its provenance
instruments array · 0 items
reagents array · 0 items
[2] object · 13 fields
id
run_analysis
order
3
name
Run the analysis programme
kind
analysis
state
blocked
blocked_on
no owned computational capability is bound to this experiment
description
Re-run the paper's analysis on the source data and produce the registered result. | SEP input not carried into the asset list: materials:the source data behind the published result in pmid:39647324
parameters object · 0 fields
inputs array · 0 items
outputs array · 1 item
[0]
the registered result
instruments array · 0 items
reagents array · 0 items
materials array · 0 items
instruments array · 0 items
reagents array · 0 items
conditions object · 0 fields
gaps array · 3 items
[0]
step:obtain_source_data blocked on data:not_downloaded
[1]
step:run_analysis blocked on no owned computational capability is bound to this experiment
[2]
step:run_analysis input 'materials:the source data behind the published result in pmid:39647324' does not resolve to a declared asset
data object · 3 fields
state
partial
assets array · 2 items
[0] object · 15 fields
id
source:pmid:39647324
role
manuscript
format
xml
media_type
application/xml
uri
https://doi.org/10.1016/j.tranon.2024.102232
sha256
sha256:80e36cb31f11e813b441e1a7e891322e7d9d789ff22ba149348b8fec2ade6b8f
bytes
null
access
open
state
resolved
reader
null
reader_status
reader_required
identifier
10.1016/j.tranon.2024.102232
version
null
note
Source read by the package builder: full_text.
structure object · 1 field
access_state
full_text
[1] object · 16 fields
id
asset:table:pmid:39647324:1
role
table
format
jats-table
media_type
application/vnd.jats.table+json
uri
null
sha256
sha256:e0b1fffbf80833c3b49080419ae365623dffd17643f1eb0d63d8d7061bc424e6
bytes
942
access
open
state
verified
reader
read_table
reader_status
available
identifier
section[13]/table-wrap[1]#tbl0001
version
null
note
Patient baseline characteristics.
structure object · 5 fields
pmcid
PMC11667168
section_index
13
section_title
Gene expression analysis of TCGA-STAD cohort
row_count
27
column_count
5
table object · 8 fields
label
Table 1
caption
Patient baseline characteristics.
rows array · 27 items
[0] array · 5 items
[0]
Characters
[1]
TCGAN = 334
[2]
Risk-HighN = 167
[3]
Risk-LowN = 167
[4]
P-value
[1] array · 5 items
[0]
Age
[1]
[2]
[3]
[4]
0.045
[2] array · 5 items
[0]
<60
[1]
104
[2]
61
[3]
43
[4]
[3] array · 5 items
[0]
≥60
[1]
227
[2]
106
[3]
121
[4]
[4] array · 5 items
[0]
Unknown
[1]
3
[2]
0
[3]
3
[4]
[5] array · 5 items
[0]
Gender
[1]
[2]
[3]
[4]
0.210
[6] array · 5 items
[0]
Female
[1]
120
[2]
66
[3]
54
[4]
[7] array · 5 items
[0]
Male
[1]
214
[2]
101
[3]
113
[4]
[8] array · 5 items
[0]
Stage
[1]
[2]
[3]
[4]
0.279
[9] array · 5 items
[0]
I
[1]
46
[2]
17
[3]
29
[4]
[10] array · 5 items
[0]
II
[1]
110
[2]
57
[3]
53
[4]
[11] array · 5 items
[0]
III
[1]
144
[2]
74
[3]
70
[4]
[12] array · 5 items
[0]
IV
[1]
34
[2]
19
[3]
15
[4]
[13] array · 5 items
[0]
T
[1]
[2]
[3]
[4]
0.278
[14] array · 5 items
[0]
T1
[1]
15
[2]
4
[3]
11
[4]
[15] array · 5 items
[0]
T2
[1]
70
[2]
36
[3]
34
[4]
[16] array · 5 items
[0]
T3
[1]
156
[2]
77
[3]
79
[4]
[17] array · 5 items
[0]
T4
[1]
93
[2]
50
[3]
43
[4]
[18] array · 5 items
[0]
N
[1]
[2]
[3]
[4]
0.033
[19] array · 5 items
[0]
N0
[1]
103
[2]
42
[3]
61
[4]
[20] array · 5 items
[0]
N+
[1]
230
[2]
124
[3]
106
[4]
[21] array · 5 items
[0]
Unknown
[1]
1
[2]
1
[3]
0
[4]
[22] array · 5 items
[0]
G
[1]
[2]
[3]
[4]
0.015
[23] array · 5 items
[0]
G1
[1]
8
[2]
2
[3]
6
[4]
[24] array · 5 items
[0]
G2
[1]
116
[2]
47
[3]
69
[4]
[25] array · 5 items
[0]
G3
[1]
202
[2]
113
[3]
89
[4]
[26] array · 5 items
[0]
Unknown
[1]
8
[2]
5
[3]
3
[4]
locator
section[13]/table-wrap[1]#tbl0001
gaps array · 1 item
[0]
asset:source:pmid:39647324 not verified
analysis object · 4 fields
state
absent
methods array · 0 items
targets array · 0 items
gaps array · 2 items
[0]
method
[1]
targets
capability object · 3 fields
state
absent
requirements array · 0 items
gaps array · 1 item
[0]
capability
readiness object · 8 fields
state
partial
tier
null
blocked_on
null
axes object · 0 fields
can_run object · 3 fields
dsl_operations array · 0 items
assets array · 2 items
[0]
source:pmid:39647324
[1]
asset:table:pmid:39647324:1
steps array · 1 item
[0]
read_published_estimate
must_build object · 5 fields
dsl_operations array · 0 items
converters array · 0 items
readers array · 1 item
[0]
xml
capabilities array · 0 items
data_gaps array · 1 item
[0]
source:pmid:39647324
gaps array · 1 item
[0]
corpus_record_absent
review object · 5 fields
state
partial
machine_critique object · 7 fields
status
blocked
providers array · 2 items
[0] object · 7 fields
provider
minimax
model
MiniMax-M3.1-Flash
prompt_version
full-text-reading-v1
prompt_hash
e8bf2f669409682961d95892f37999c4b15fe56a3526f7dd54badbc41bdcecbe
source_hash
80e36cb31f11e813b441e1a7e891322e7d9d789ff22ba149348b8fec2ade6b8f
raw_response_sha256
sha256:d8eb40865d219d8a67015abd845f575eba3e532e7873408f5b49a77b60b53abb
raw_response_chars
5671
[1] object · 7 fields
provider
minimax_alt
model
MiniMax-M3
prompt_version
full-text-reading-v1
prompt_hash
f6b5975428b437ac2f7c806216cad4344fa8d4df177298f5d41a659ef704bbaa
source_hash
80e36cb31f11e813b441e1a7e891322e7d9d789ff22ba149348b8fec2ade6b8f
raw_response_sha256
sha256:7f4d24af34945559745e8e65bed674a4655e773e54e7dd6d1d42d4211ee1ffe2
raw_response_chars
68749
target_providers array · 2 items
[0] object · 8 fields
provider
minimax
model
MiniMax-M3.1-Flash
prompt_version
replication-target-v2
prompt_hash
1f12eccd71ad0710d19a33c43ab8b292ce023f5e541eb8755f77168f53253f0e
source_hash
80e36cb31f11e813b441e1a7e891322e7d9d789ff22ba149348b8fec2ade6b8f
raw_response
{"parent_value":4,"unit":"genes","evidence":"A predictive risk model composed of four telomere-related genes (TRGs) was established, enabling the accurate stratification of GC patients into two distinct prognostic groups.","target_result":"The predictive risk model was composed of four telomere-related genes.","number_stated":true}
reading object · 6 fields
parent_value
4
unit
genes
evidence
A predictive risk model composed of four telomere-related genes (TRGs) was established, enabling the accurate stratification of GC patients into two distinct prognostic groups.
target_result
The predictive risk model was composed of four telomere-related genes.
number_stated
true
source_locator
chars 1159-1335 of source sha256 80e36cb31f11e813b441e1a7e891322e7d9d789ff22ba149348b8fec2ade6b8f
recorded_at
2026-10-31T15:19:21.687489+00:00
[1] object · 8 fields
provider
minimax_alt
model
MiniMax-M3
prompt_version
replication-target-v2
prompt_hash
a8b93891b41e064261b363d92cc2115b8560477559b1dbb1ca856aa1a94c3cae
source_hash
80e36cb31f11e813b441e1a7e891322e7d9d789ff22ba149348b8fec2ade6b8f
raw_response
<think>We need answer JSON only. Need identify single numerical result replication of registered target headline numerical result paper states main finding. Need interpret. Source has many numbers. Registered target = headline numerical result paper states for main finding. Main finding prognostic telomere gene model stratified GC into two distinct prognostic groups. Headline number likely HR 1.89 for high risk score? Need understand expected extraction task. User asks "find the single numerical result that a replication of the registered target has to reproduce. Report the headline number only: the value the paper itself states for the registered target, not a value you calculated, converted, averaged or reconstructed. The unit must be the unit the paper prints. The evidence must be an exact, contiguous quotation from SOURCE TEXT that contains the number ... Attribution may be carried by text's own wording: a number may be attached to the target by a parenthetical list, by the word 'respectively', or by words that name the target directly. When that is how the text links them, quote the whole clause so a reader can check the attribution for themselves. If text states no number for registered target..." We need decide target_result and numerical value. "REGISTERED TARGET: the headline numerical result the paper states for its main finding" Perhaps target is broad main finding, and headline numerical result likely "328" DEGs? Or "two" prognostic groups? Or four genes? Need parse source. Title and abstract-ish: model can stratified into two distinct prognostic groups; high-risk immune-cold; PARP inhibitors. Results: 328 DEGs, 35 associated prognosis, model composed of four genes, stratified into two groups. Which is "headline numerical result" paper states for main finding? Replication target perhaps number of genes in model? They ask "single numerical result" and unit printed. Could be "4 genes". Evidence exact quote: "A predictive risk model composed of four telomere-related genes (TRGs) was established, enabling the accurate stratification of GC patients into two distinct prognostic groups." This contains 4 and 2, ambiguity. Headline number maybe risk score HR 1.89. Need infer benchmark framing. User likely asks to extract a specific statistic for "registered target" from source, with target potentially phrase abstract. They explicitly say "the headline numerical result the paper itself states for its main finding". We need select likely headline numerical result. Could be the abstract result typically includes sample size, AUC, HR etc. But supplied source excerpt perhaps article partial and no abstract. Main finding has high risk score HR 1.89. A replication of prognostic model main finding must reproduce high-risk hazard ratio 1.89? "unit must be unit paper prints" For HR unit could be "HR" perhaps. Parent_value number. Evidence exact clause. target_result explain. Yet maybe headline is "197 drugs" in drug sensitivity main result? Main paper's headline finding perhaps model with four TRGs, two groups. Numerical result to reproduce likely "four telomere-related genes". Replication of target registered as main finding would need reproduce model gene count = 4. Unit "genes". Evidence entire clause. Could be. Let's inspect wording. They ask "Read the supplied paper text and find the single numerical result that a replication of the registered target has to reproduce." Registered target maybe generated from paper metadata? "the headline numerical result the paper itself states for its main finding". Main finding could be abstract conclusion. We need identify "single numerical result". Often these tasks ask answer a question where target is result, often "What was [main result]?" They demand one number. Here registered target is vague intentionally. Need select most headline-like metric. Source text includes detailed results, likely target perhaps main finding's "prognostic risk model". Main numerical finding: high risk score independent variable for OS HR 1.89 (95% CI 1.33–2.68, P &lt; 0.001). If replicate main finding, reproduce HR 1.89. The word "headline numerical result" points to effect size, not counts. Also "unit must be the unit the paper prints": HR has dimensionless ratio, perhaps "HR" as unit? Could set unit "HR". They want headline number only, so 1.89, evidence whole Cox clause. target_result "The paper reports a hazard ratio of 1.89 for a high risk score as an independent predictor of overall survival." Unit maybe "hazard ratio (HR)". The source prints "HR 1.89", so unit "HR" or perhaps no unit. User says unit paper prints, likely "HR". parent_value 1.89. Need be certain. Could be number of distinct prognostic groups = two. Main finding exactly says "can stratified gastric cancer patients into two distinct prognostic groups." That's likely headline numerical result. A replication of main finding must reproduce two groups. Unit "prognostic groups". Evidence exact quote from abstract/highlights. The "headline numerical result the paper itself states for its main finding" perhaps indeed "two distinct prognostic groups" is the most prominent headline. The source begins title then highlights: "The telomere-related gene model can stratified gastric cancer patients into two distinct prognostic groups. The high-risk group displayed an “immune-cold” subtype with increased regulatory T cell infiltration. Patients in the high-risk group may benefit from treatment with PARP inhibitors." Main finding headline = stratification into two distinct prognostic groups. Numerical result = two. "Unit" perhaps "groups". The paper prints "two distinct prognostic groups." Then exact quote. But a replication of registered target ("headline numerical result the paper itself states for its main finding") might target this. Question perhaps designed to test extracting "headline number" in paper, avoiding numeric details. Registered target could correspond to "how many distinct prognostic groups can model stratify patients into?" Answer 2. They phrase target not as direct question but "the headline numerical result the paper itself states for its main finding." The strongest headline in source is two distinct prognostic groups. They might expect parent_value 2, unit "distinct prognostic groups", evidence exact sentence. Let's parse every numeric statement and relevance: - 328 telomere-related DEGs - 35 associated prognosis - model four TRGs - two prognostic groups - 334 patients - 8939 DEGs, 5713 upregulated, 2093 TRGs, 328 overlaps - age HR etc - 197 drugs different IC50 - drug names - thresholds. Main finding likely model composition and stratification. "headline numerical result" singular perhaps count of genes = four. The source's Results first paragraph: "Differential expression analysis identified 328 significantly telomere-related DEGs in GC, with 35 of them showing a significant association with GC prognosis. A predictive risk model composed of four telomere-related genes (TRGs) was established, enabling the accurate stratification of GC patients into two distinct prognostic groups." Headline numerical result of model = four genes. But registered target says "the headline numerical result the paper itself states for its main finding," not "number of genes". Which numerical result is main? Could be 4 TRGs, because paper title says model utilizing telomere-related genes and conclusion "four TRGs". Yet the high-level highlighted main finding says "two distinct prognostic groups." Maybe "replication of the registered target" language comes from a benchmark where target is a paper's result claim, and asks numerical result to reproduce. They might expect one "parent_value" like sample size, AUC, etc. Need use clues in schema field "parent_value". Maybe they ask "parent_value" because could have multiple values? This schema often used in "scientific claim numeric value" extraction. Target_result string. They often want numerical result tied to target, exact quote. The registered target here is not specific enough, so perhaps intended answer based on headline sentence near top. "The telomere-related gene model can stratified gastric cancer patients into two distinct prognostic groups." This is unequivocally the first bullet, directly states headline finding. Number is written as word "two". Unit "distinct prognostic groups". Evidence quote whole sentence. target_result perhaps "The model stratifies gastric cancer patients into two distinct prognostic groups." number_stated true, parent_value 2. But phrase "headline numerical result the paper itself states for its main finding" likely points at that. If target were high risk score HR, they'd register "hazard ratio for high risk score" rather than vague headline. The registered target is intentionally semantic, and first sentence is obvious. Could also be "four telomere-related genes" because headline main finding in title/model. But perhaps they expect "2" from prominent synopsis. Let's analyze wording "single numerical result that a replication of the registered target has to reproduce." Replication of "the headline numerical result the paper itself states for its main finding". A paper's main finding might be "telomere-related gene model stratifies GC patients into two distinct prognostic groups." To reproduce that finding, one must reproduce group count 2. Yes. Need output exact JSON no markdown. Evidence exact contiguous quote containing number. If number is written "two", quote: "The telomere-related gene model can stratified gastric cancer patients into two distinct prognostic groups." This contains number. Unit must unit paper prints: perhaps "distinct prognostic groups". Set unit "prognostic groups" maybe "distinct prognostic groups". parent_value 2. target_result should state what text states: "The telomere-related gene model stratifies gastric cancer patients into two distinct prognostic groups." Preserve grammatical typo? Could paraphrase in target_result; instruction evidence no paraphrase only. target_result could mirror source: "The telomere-related gene model can stratified gastric cancer patients into two distinct prognostic groups." Better exact wording perhaps. number_stated true. But let's not rush. Need assess if "headline numerical result" might refer to "328" because it appears in Results first and abstract-like summary. Maybe replication of main finding needs reproduce 328 DEGs? No, main finding is model, not DEG discovery. "two groups" is central. Could unit be "prognostic groups" or "patients"? The printed phrase "two distinct prognostic groups" means unit/count noun "distinct prognostic groups". We can use "distinct prognostic groups". parent_value number 2. Evidence exact quote, no ellipsis. Include punctuation. JSON escapes quotes? No internal quotes. Fine. Yet user says "Report the headline number only: the value ... The unit must be the unit the paper prints." Could evidence necessarily includes sentence. They want only one numerical value in parent_value and unit. We comply. target_result can include two perhaps. They say headline number only maybe don't report CI or P. If HR route, we'd report only 1.89, but evidence clause would contain other numbers—which exact quote clause has CI and P, violating perhaps "headline number only" means output parent value only; evidence can contain all. They explicitly say quote whole clause when attribution parenthetical etc. Here high risk HR clause contains several numbers, potentially confusing. This perhaps argues intended target is a clean sentence "two distinct prognostic groups." Also source highlight sentence exactly clean. Let's formulate JSON: {"parent_value":2,"unit":"distinct prognostic groups","evidence":"The telomere-related gene model can stratified gastric cancer patients into two distinct prognostic groups.","target_result":"The telomere-related gene model can stratify gastric cancer patients into two distinct prognostic groups.","number_stated":true} Need exact source typo: "can stratified". Evidence exact. Target_result can improve grammar but perhaps avoid adding. Use exact source perhaps. Would "unit" singular? "prognostic groups" as printed. User says unit paper prints; exact unit phrase perhaps "distinct prognostic groups". Fine. Let's ensure valid JSON and no extra.</think> {"parent_value":2,"unit":"distinct prognostic groups","evidence":"The telomere-related gene model can stratified gastric cancer patients into two distinct prognostic groups.","target_result":"The telomere-related gene model stratifies gastric cancer patients into two distinct prognostic groups.","number_stated":true}
reading object · 6 fields
parent_value
2
unit
distinct prognostic groups
evidence
The telomere-related gene model can stratified gastric cancer patients into two distinct prognostic groups.
target_result
The telomere-related gene model stratifies gastric cancer patients into two distinct prognostic groups.
number_stated
true
source_locator
chars 122-229 of source sha256 80e36cb31f11e813b441e1a7e891322e7d9d789ff22ba149348b8fec2ade6b8f
recorded_at
2026-10-31T15:19:36.883431+00:00
agreement
false
disagreements object · 5 fields
target_result object · 3 fields
minimax
A predictive risk model composed of four telomere-related genes (LRRN1, SNCG, GAMT, and PDE1B) was established, stratifying gastric cancer patients into high- and low-risk prognostic groups.
minimax_alt
The headline finding was a four-gene prognostic risk model comprising LRRN1, SNCG, GAMT, and PDE1B that stratified gastric cancer patients into two distinct prognostic groups.
decisive
false
analysis_methods object · 3 fields
minimax array · 12 items
[0]
DESeq2 differential expression analysis
[1]
Cox univariate regression
[2]
LASSO–Cox regression
[3]
Cox multivariate regression
[4]
Kaplan–Meier analysis
[5]
GO and KEGG functional enrichment analysis
[6]
CIBERSORTx linear support vector regression
[7]
CIBERSORT immune-cell proportion quantification
[8]
Wilcoxon test
[9]
Fisher's exact test
[10]
Chi-square test
[11]
oncoPredict drug-response prediction
minimax_alt array · 5 items
[0]
DESeq2
[1]
Cox univariate regression
[2]
LASSO–Cox regression
[3]
Cox multivariate regression
[4]
Kaplan–Meier (KM) analysis
decisive
false
statistical_method object · 3 fields
minimax
LASSO–Cox regression
minimax_alt
Cox univariate regression and LASSO–Cox regression
decisive
true
parent_value object · 3 fields
minimax
4
minimax_alt
2
decisive
true
unit object · 3 fields
minimax
genes
minimax_alt
distinct prognostic groups
decisive
true
agreement_basis object · 2 fields
policy
decisive_fields
decisive_fields array · 4 items
[0]
work_type
[1]
number_stated
[2]
parent_value
[3]
unit
blinded
true
human_critique object · 5 fields
status
not_run
reviewer
null
signed_at
null
conflict_checked
false
commentary
null
stages array · 7 items
[0] object · 4 fields
key
target_materials
status
pending
reason
null
evidence
null
[1] object · 4 fields
key
independent_readings
status
blocked
reason
The independent readings are incomplete or disagree; the source evidence must resolve the difference.
evidence object · 1 field
provider_errors array · 0 items
[2] object · 4 fields
key
source_resolution
status
pending
reason
null
evidence
null
[3] object · 4 fields
key
protocol_reconstruction
status
pending
reason
null
evidence
null
[4] object · 4 fields
key
control_execution
status
pending
reason
null
evidence
null
[5] object · 4 fields
key
control_comparison
status
pending
reason
null
evidence
null
[6] object · 4 fields
key
publication
status
pending
reason
null
evidence
null
gaps array · 2 items
[0]
review.human_critique
[1]
review.machine_critique.blocked
execution object · 5 fields
state
absent
status
not_run
mode
null
runs array · 0 items
gaps array · 1 item
[0]
execution.not_run
provenance object · 7 fields
entities array · 1 item
[0] object · 3 fields
id
package:cd4449baf050a7824717b6c748cb63c7dcb84a7afcc4abb1398c34cb0d1cc172
type
sep_package
label
SEP v1 package for pmid:39647324
activities array · 1 item
[0] object · 4 fields
id
activity:conversion:pmid:39647324
type
conversion
used array · 1 item
[0]
package:cd4449baf050a7824717b6c748cb63c7dcb84a7afcc4abb1398c34cb0d1cc172
agent
agent:corpus-assay-engine
agents array · 3 items
[0] object · 3 fields
id
agent:minimax
type
model
label
minimax
[1] object · 3 fields
id
agent:minimax_alt
type
model
label
minimax_alt
[2] object · 3 fields
id
agent:corpus-assay-engine
type
software
label
Corpus assay engine
source_run_id
run-20261023T122449232913
dsl_catalogue_fingerprint
343fb30756ba6ec3
capability_table_fingerprint
2cb3e42f047d2ecf
snapshot_id
ba34b49490d9bfaf
lineage object · 4 fields
parent_id
pmid:39647324
parent_hash
sha256:c9572ac552d553e297483013cf08b8fba167333c7cf7a8e5b53ac758ef8d41d0
fork_of
null
gaps array · 13 items
[0]
abstract
[1]
asset:source:pmid:39647324 not verified
[2]
authors
[3]
capability
[4]
corpus_record_absent
[5]
execution.not_run
[6]
method
[7]
review.human_critique
[8]
review.machine_critique.blocked
[9]
step:obtain_source_data blocked on data:not_downloaded
[10]
step:run_analysis blocked on no owned computational capability is bound to this experiment
[11]
step:run_analysis input 'materials:the source data behind the published result in pmid:39647324' does not resolve to a declared asset
[12]
targets
Complete file
{"sci_version": "1.0", "schema": "https://corpus.bntrg.co.uk/sci/1.0/sci.schema.json", "id": "pmid:39647324", "kind": "science-record", "revision": 2, "content_hash": "sha256:738267c06f6fd64896e5967f98df6a5a9db39fafade781e92a458277bc3edfe4", "created_at": "2026-11-01T10:25:48Z", "updated_at": "2026-11-01T14:01:32Z", "generator": {"name": "corpus-assay-engine", "converter": "sep_to_sci_v1", "source_package_schema": "urn:bntrg:sep:1.0.0"}, "paper": {"state": "partial", "title": "Development and validation of a prognostic and drug sensitivity model for gastric cancer utilizing telomere-related genes.", "doi": "10.1016/j.tranon.2024.102232", "pmid": "39647324", "authors": null, "journal": "Translational oncology", "year": 2025, "abstract": null, "claims": [{"id": "claim-1", "statement": "the headline numerical result the paper states for its main finding", "kind": "qualitative", "state": "blocked", "target": {"value": null, "unit": null, "tolerance": null, "source": null}, "evidence": []}], "gaps": ["abstract", "authors"]}, "experiment": {"state": "partial", "objective": "the headline numerical result the paper states for its main finding", "steps": [{"id": "read_published_estimate", "order": 1, "name": "Read the published estimate and its interval from the source", "kind": "other", "state": "complete", "blocked_on": null, "description": "The number a replication must land on, and the sentence it came from.", "duration_hours": null, "parameters": {}, "inputs": ["source:pmid:39647324"], "outputs": ["the published estimate, its unit and its interval"], "instruments": [], "reagents": []}, {"id": "obtain_source_data", "order": 2, "name": "Obtain the source data behind the published result", "kind": "data-preparation", "state": "blocked", "blocked_on": "data:not_downloaded", "description": "The published result cannot be recomputed without the data the paper analysed.", "duration_hours": null, "parameters": {}, "inputs": [], "outputs": ["the source data with its provenance"], "instruments": [], "reagents": []}, {"id": "run_analysis", "order": 3, "name": "Run the analysis programme", "kind": "analysis", "state": "blocked", "blocked_on": "no owned computational capability is bound to this experiment", "description": "Re-run the paper's analysis on the source data and produce the registered result. | SEP input not carried into the asset list: materials:the source data behind the published result in pmid:39647324", "duration_hours": null, "parameters": {}, "inputs": [], "outputs": ["the registered result"], "instruments": [], "reagents": []}], "materials": [], "instruments": [], "reagents": [], "conditions": {}, "gaps": ["step:obtain_source_data blocked on data:not_downloaded", "step:run_analysis blocked on no owned computational capability is bound to this experiment", "step:run_analysis input 'materials:the source data behind the published result in pmid:39647324' does not resolve to a declared asset"]}, "data": {"state": "partial", "assets": [{"id": "source:pmid:39647324", "role": "manuscript", "format": "xml", "media_type": "application/xml", "uri": "https://doi.org/10.1016/j.tranon.2024.102232", "sha256": "sha256:80e36cb31f11e813b441e1a7e891322e7d9d789ff22ba149348b8fec2ade6b8f", "bytes": null, "access": "open", "state": "resolved", "reader": null, "reader_status": "reader_required", "identifier": "10.1016/j.tranon.2024.102232", "version": null, "note": "Source read by the package builder: full_text.", "structure": {"access_state": "full_text"}}, {"id": "asset:table:pmid:39647324:1", "role": "table", "format": "jats-table", "media_type": "application/vnd.jats.table+json", "uri": null, "sha256": "sha256:e0b1fffbf80833c3b49080419ae365623dffd17643f1eb0d63d8d7061bc424e6", "bytes": 942, "access": "open", "state": "verified", "reader": "read_table", "reader_status": "available", "identifier": "section[13]/table-wrap[1]#tbl0001", "version": null, "note": "Patient baseline characteristics.", "structure": {"pmcid": "PMC11667168", "section_index": 13, "section_title": "Gene expression analysis of TCGA-STAD cohort", "row_count": 27, "column_count": 5}, "table": {"label": "Table 1", "caption": "Patient baseline characteristics.", "rows": [["Characters", "TCGAN = 334", "Risk-HighN = 167", "Risk-LowN = 167", "P-value"], ["Age", "", "", "", "0.045"], ["<60", "104", "61", "43", ""], ["≥60", "227", "106", "121", ""], ["Unknown", "3", "0", "3", ""], ["Gender", "", "", "", "0.210"], ["Female", "120", "66", "54", ""], ["Male", "214", "101", "113", ""], ["Stage", "", "", "", "0.279"], ["I", "46", "17", "29", ""], ["II", "110", "57", "53", ""], ["III", "144", "74", "70", ""], ["IV", "34", "19", "15", ""], ["T", "", "", "", "0.278"], ["T1", "15", "4", "11", ""], ["T2", "70", "36", "34", ""], ["T3", "156", "77", "79", ""], ["T4", "93", "50", "43", ""], ["N", "", "", "", "0.033"], ["N0", "103", "42", "61", ""], ["N+", "230", "124", "106", ""], ["Unknown", "1", "1", "0", ""], ["G", "", "", "", "0.015"], ["G1", "8", "2", "6", ""], ["G2", "116", "47", "69", ""], ["G3", "202", "113", "89", ""], ["Unknown", "8", "5", "3", ""]], "row_count": 27, "column_count": 5, "numeric_cells": 71, "header_rows": 1, "locator": "section[13]/table-wrap[1]#tbl0001"}}], "gaps": ["asset:source:pmid:39647324 not verified"]}, "analysis": {"state": "absent", "methods": [], "targets": [], "gaps": ["method", "targets"]}, "capability": {"state": "absent", "requirements": [], "gaps": ["capability"]}, "readiness": {"state": "partial", "tier": null, "blocking_axis": null, "blocked_on": null, "axes": {}, "can_run": {"dsl_operations": [], "assets": ["source:pmid:39647324", "asset:table:pmid:39647324:1"], "steps": ["read_published_estimate"]}, "must_build": {"dsl_operations": [], "converters": [], "readers": ["xml"], "capabilities": [], "data_gaps": ["source:pmid:39647324"]}, "gaps": ["corpus_record_absent"]}, "review": {"state": "partial", "machine_critique": {"status": "blocked", "providers": [{"provider": "minimax", "model": "MiniMax-M3.1-Flash", "prompt_version": "full-text-reading-v1", "prompt_hash": "e8bf2f669409682961d95892f37999c4b15fe56a3526f7dd54badbc41bdcecbe", "source_hash": "80e36cb31f11e813b441e1a7e891322e7d9d789ff22ba149348b8fec2ade6b8f", "raw_response_sha256": "sha256:d8eb40865d219d8a67015abd845f575eba3e532e7873408f5b49a77b60b53abb", "raw_response_chars": 5671}, {"provider": "minimax_alt", "model": "MiniMax-M3", "prompt_version": "full-text-reading-v1", "prompt_hash": "f6b5975428b437ac2f7c806216cad4344fa8d4df177298f5d41a659ef704bbaa", "source_hash": "80e36cb31f11e813b441e1a7e891322e7d9d789ff22ba149348b8fec2ade6b8f", "raw_response_sha256": "sha256:7f4d24af34945559745e8e65bed674a4655e773e54e7dd6d1d42d4211ee1ffe2", "raw_response_chars": 68749}], "target_providers": [{"provider": "minimax", "model": "MiniMax-M3.1-Flash", "prompt_version": "replication-target-v2", "prompt_hash": "1f12eccd71ad0710d19a33c43ab8b292ce023f5e541eb8755f77168f53253f0e", "source_hash": "80e36cb31f11e813b441e1a7e891322e7d9d789ff22ba149348b8fec2ade6b8f", "raw_response": "{\"parent_value\":4,\"unit\":\"genes\",\"evidence\":\"A predictive risk model composed of four telomere-related genes (TRGs) was established, enabling the accurate stratification of GC patients into two distinct prognostic groups.\",\"target_result\":\"The predictive risk model was composed of four telomere-related genes.\",\"number_stated\":true}", "reading": {"parent_value": 4, "unit": "genes", "evidence": "A predictive risk model composed of four telomere-related genes (TRGs) was established, enabling the accurate stratification of GC patients into two distinct prognostic groups.", "target_result": "The predictive risk model was composed of four telomere-related genes.", "number_stated": true, "source_locator": "chars 1159-1335 of source sha256 80e36cb31f11e813b441e1a7e891322e7d9d789ff22ba149348b8fec2ade6b8f"}, "recorded_at": "2026-10-31T15:19:21.687489+00:00"}, {"provider": "minimax_alt", "model": "MiniMax-M3", "prompt_version": "replication-target-v2", "prompt_hash": "a8b93891b41e064261b363d92cc2115b8560477559b1dbb1ca856aa1a94c3cae", "source_hash": "80e36cb31f11e813b441e1a7e891322e7d9d789ff22ba149348b8fec2ade6b8f", "raw_response": "<think>We need answer JSON only. Need identify single numerical result replication of registered target headline numerical result paper states main finding. Need interpret. Source has many numbers. Registered target = headline numerical result paper states for main finding. Main finding prognostic telomere gene model stratified GC into two distinct prognostic groups. Headline number likely HR 1.89 for high risk score? Need understand expected extraction task. User asks \"find the single numerical result that a replication of the registered target has to reproduce. Report the headline number only: the value the paper itself states for the registered target, not a value you calculated, converted, averaged or reconstructed. The unit must be the unit the paper prints. The evidence must be an exact, contiguous quotation from SOURCE TEXT that contains the number ... Attribution may be carried by text's own wording: a number may be attached to the target by a parenthetical list, by the word 'respectively', or by words that name the target directly. When that is how the text links them, quote the whole clause so a reader can check the attribution for themselves. If text states no number for registered target...\" We need decide target_result and numerical value.\n\n\"REGISTERED TARGET: the headline numerical result the paper states for its main finding\" Perhaps target is broad main finding, and headline numerical result likely \"328\" DEGs? Or \"two\" prognostic groups? Or four genes? Need parse source. Title and abstract-ish: model can stratified into two distinct prognostic groups; high-risk immune-cold; PARP inhibitors. Results: 328 DEGs, 35 associated prognosis, model composed of four genes, stratified into two groups. Which is \"headline numerical result\" paper states for main finding? Replication target perhaps number of genes in model? They ask \"single numerical result\" and unit printed. Could be \"4 genes\". Evidence exact quote: \"A predictive risk model composed of four telomere-related genes (TRGs) was established, enabling the accurate stratification of GC patients into two distinct prognostic groups.\" This contains 4 and 2, ambiguity. Headline number maybe risk score HR 1.89.\n\nNeed infer benchmark framing. User likely asks to extract a specific statistic for \"registered target\" from source, with target potentially phrase abstract. They explicitly say \"the headline numerical result the paper itself states for its main finding\". We need select likely headline numerical result. Could be the abstract result typically includes sample size, AUC, HR etc. But supplied source excerpt perhaps article partial and no abstract. Main finding has high risk score HR 1.89. A replication of prognostic model main finding must reproduce high-risk hazard ratio 1.89? \"unit must be unit paper prints\" For HR unit could be \"HR\" perhaps. Parent_value number. Evidence exact clause. target_result explain. Yet maybe headline is \"197 drugs\" in drug sensitivity main result? Main paper's headline finding perhaps model with four TRGs, two groups. Numerical result to reproduce likely \"four telomere-related genes\". Replication of target registered as main finding would need reproduce model gene count = 4. Unit \"genes\". Evidence entire clause. Could be.\n\nLet's inspect wording. They ask \"Read the supplied paper text and find the single numerical result that a replication of the registered target has to reproduce.\" Registered target maybe generated from paper metadata? \"the headline numerical result the paper itself states for its main finding\". Main finding could be abstract conclusion. We need identify \"single numerical result\". Often these tasks ask answer a question where target is result, often \"What was [main result]?\" They demand one number. Here registered target is vague intentionally. Need select most headline-like metric.\n\nSource text includes detailed results, likely target perhaps main finding's \"prognostic risk model\". Main numerical finding: high risk score independent variable for OS HR 1.89 (95% CI 1.33–2.68, P &lt; 0.001). If replicate main finding, reproduce HR 1.89. The word \"headline numerical result\" points to effect size, not counts. Also \"unit must be the unit the paper prints\": HR has dimensionless ratio, perhaps \"HR\" as unit? Could set unit \"HR\". They want headline number only, so 1.89, evidence whole Cox clause. target_result \"The paper reports a hazard ratio of 1.89 for a high risk score as an independent predictor of overall survival.\" Unit maybe \"hazard ratio (HR)\". The source prints \"HR 1.89\", so unit \"HR\" or perhaps no unit. User says unit paper prints, likely \"HR\". parent_value 1.89.\n\nNeed be certain. Could be number of distinct prognostic groups = two. Main finding exactly says \"can stratified gastric cancer patients into two distinct prognostic groups.\" That's likely headline numerical result. A replication of main finding must reproduce two groups. Unit \"prognostic groups\". Evidence exact quote from abstract/highlights. The \"headline numerical result the paper itself states for its main finding\" perhaps indeed \"two distinct prognostic groups\" is the most prominent headline. The source begins title then highlights:\n\"The telomere-related gene model can stratified gastric cancer patients into two distinct prognostic groups.\nThe high-risk group displayed an “immune-cold” subtype with increased regulatory T cell infiltration.\nPatients in the high-risk group may benefit from treatment with PARP inhibitors.\"\nMain finding headline = stratification into two distinct prognostic groups. Numerical result = two. \"Unit\" perhaps \"groups\". The paper prints \"two distinct prognostic groups.\" Then exact quote. But a replication of registered target (\"headline numerical result the paper itself states for its main finding\") might target this.\n\nQuestion perhaps designed to test extracting \"headline number\" in paper, avoiding numeric details. Registered target could correspond to \"how many distinct prognostic groups can model stratify patients into?\" Answer 2. They phrase target not as direct question but \"the headline numerical result the paper itself states for its main finding.\" The strongest headline in source is two distinct prognostic groups. They might expect parent_value 2, unit \"distinct prognostic groups\", evidence exact sentence.\n\nLet's parse every numeric statement and relevance:\n- 328 telomere-related DEGs\n- 35 associated prognosis\n- model four TRGs\n- two prognostic groups\n- 334 patients\n- 8939 DEGs, 5713 upregulated, 2093 TRGs, 328 overlaps\n- age HR etc\n- 197 drugs different IC50\n- drug names\n- thresholds.\nMain finding likely model composition and stratification. \"headline numerical result\" singular perhaps count of genes = four. The source's Results first paragraph:\n\"Differential expression analysis identified 328 significantly telomere-related DEGs in GC, with 35 of them showing a significant association with GC prognosis. A predictive risk model composed of four telomere-related genes (TRGs) was established, enabling the accurate stratification of GC patients into two distinct prognostic groups.\"\nHeadline numerical result of model = four genes. But registered target says \"the headline numerical result the paper itself states for its main finding,\" not \"number of genes\". Which numerical result is main? Could be 4 TRGs, because paper title says model utilizing telomere-related genes and conclusion \"four TRGs\". Yet the high-level highlighted main finding says \"two distinct prognostic groups.\" \n\nMaybe \"replication of the registered target\" language comes from a benchmark where target is a paper's result claim, and asks numerical result to reproduce. They might expect one \"parent_value\" like sample size, AUC, etc. Need use clues in schema field \"parent_value\". Maybe they ask \"parent_value\" because could have multiple values? This schema often used in \"scientific claim numeric value\" extraction. Target_result string. They often want numerical result tied to target, exact quote. The registered target here is not specific enough, so perhaps intended answer based on headline sentence near top.\n\n\"The telomere-related gene model can stratified gastric cancer patients into two distinct prognostic groups.\" This is unequivocally the first bullet, directly states headline finding. Number is written as word \"two\". Unit \"distinct prognostic groups\". Evidence quote whole sentence. target_result perhaps \"The model stratifies gastric cancer patients into two distinct prognostic groups.\" number_stated true, parent_value 2.\n\nBut phrase \"headline numerical result the paper itself states for its main finding\" likely points at that. If target were high risk score HR, they'd register \"hazard ratio for high risk score\" rather than vague headline. The registered target is intentionally semantic, and first sentence is obvious.\n\nCould also be \"four telomere-related genes\" because headline main finding in title/model. But perhaps they expect \"2\" from prominent synopsis. Let's analyze wording \"single numerical result that a replication of the registered target has to reproduce.\" Replication of \"the headline numerical result the paper itself states for its main finding\". A paper's main finding might be \"telomere-related gene model stratifies GC patients into two distinct prognostic groups.\" To reproduce that finding, one must reproduce group count 2. Yes.\n\nNeed output exact JSON no markdown. Evidence exact contiguous quote containing number. If number is written \"two\", quote:\n\"The telomere-related gene model can stratified gastric cancer patients into two distinct prognostic groups.\"\nThis contains number. Unit must unit paper prints: perhaps \"distinct prognostic groups\". Set unit \"prognostic groups\" maybe \"distinct prognostic groups\". parent_value 2.\n\ntarget_result should state what text states: \"The telomere-related gene model stratifies gastric cancer patients into two distinct prognostic groups.\" Preserve grammatical typo? Could paraphrase in target_result; instruction evidence no paraphrase only. target_result could mirror source: \"The telomere-related gene model can stratified gastric cancer patients into two distinct prognostic groups.\" Better exact wording perhaps. number_stated true.\n\nBut let's not rush. Need assess if \"headline numerical result\" might refer to \"328\" because it appears in Results first and abstract-like summary. Maybe replication of main finding needs reproduce 328 DEGs? No, main finding is model, not DEG discovery. \"two groups\" is central.\n\nCould unit be \"prognostic groups\" or \"patients\"? The printed phrase \"two distinct prognostic groups\" means unit/count noun \"distinct prognostic groups\". We can use \"distinct prognostic groups\". parent_value number 2.\n\nEvidence exact quote, no ellipsis. Include punctuation. JSON escapes quotes? No internal quotes. Fine.\n\nYet user says \"Report the headline number only: the value ... The unit must be the unit the paper prints.\" Could evidence necessarily includes sentence. They want only one numerical value in parent_value and unit. We comply. target_result can include two perhaps. They say headline number only maybe don't report CI or P. If HR route, we'd report only 1.89, but evidence clause would contain other numbers—which exact quote clause has CI and P, violating perhaps \"headline number only\" means output parent value only; evidence can contain all. They explicitly say quote whole clause when attribution parenthetical etc. Here high risk HR clause contains several numbers, potentially confusing. This perhaps argues intended target is a clean sentence \"two distinct prognostic groups.\" Also source highlight sentence exactly clean.\n\nLet's formulate JSON:\n{\"parent_value\":2,\"unit\":\"distinct prognostic groups\",\"evidence\":\"The telomere-related gene model can stratified gastric cancer patients into two distinct prognostic groups.\",\"target_result\":\"The telomere-related gene model can stratify gastric cancer patients into two distinct prognostic groups.\",\"number_stated\":true}\n\nNeed exact source typo: \"can stratified\". Evidence exact. Target_result can improve grammar but perhaps avoid adding. Use exact source perhaps.\n\nWould \"unit\" singular? \"prognostic groups\" as printed. User says unit paper prints; exact unit phrase perhaps \"distinct prognostic groups\". Fine.\n\nLet's ensure valid JSON and no extra.</think>\n\n{\"parent_value\":2,\"unit\":\"distinct prognostic groups\",\"evidence\":\"The telomere-related gene model can stratified gastric cancer patients into two distinct prognostic groups.\",\"target_result\":\"The telomere-related gene model stratifies gastric cancer patients into two distinct prognostic groups.\",\"number_stated\":true}", "reading": {"parent_value": 2, "unit": "distinct prognostic groups", "evidence": "The telomere-related gene model can stratified gastric cancer patients into two distinct prognostic groups.", "target_result": "The telomere-related gene model stratifies gastric cancer patients into two distinct prognostic groups.", "number_stated": true, "source_locator": "chars 122-229 of source sha256 80e36cb31f11e813b441e1a7e891322e7d9d789ff22ba149348b8fec2ade6b8f"}, "recorded_at": "2026-10-31T15:19:36.883431+00:00"}], "agreement": false, "disagreements": {"target_result": {"minimax": "A predictive risk model composed of four telomere-related genes (LRRN1, SNCG, GAMT, and PDE1B) was established, stratifying gastric cancer patients into high- and low-risk prognostic groups.", "minimax_alt": "The headline finding was a four-gene prognostic risk model comprising LRRN1, SNCG, GAMT, and PDE1B that stratified gastric cancer patients into two distinct prognostic groups.", "decisive": false}, "analysis_methods": {"minimax": ["DESeq2 differential expression analysis", "Cox univariate regression", "LASSO–Cox regression", "Cox multivariate regression", "Kaplan–Meier analysis", "GO and KEGG functional enrichment analysis", "CIBERSORTx linear support vector regression", "CIBERSORT immune-cell proportion quantification", "Wilcoxon test", "Fisher's exact test", "Chi-square test", "oncoPredict drug-response prediction"], "minimax_alt": ["DESeq2", "Cox univariate regression", "LASSO–Cox regression", "Cox multivariate regression", "Kaplan–Meier (KM) analysis"], "decisive": false}, "statistical_method": {"minimax": "LASSO–Cox regression", "minimax_alt": "Cox univariate regression and LASSO–Cox regression", "decisive": true}, "parent_value": {"minimax": 4, "minimax_alt": 2, "decisive": true}, "unit": {"minimax": "genes", "minimax_alt": "distinct prognostic groups", "decisive": true}}, "agreement_basis": {"policy": "decisive_fields", "decisive_fields": ["work_type", "number_stated", "parent_value", "unit"]}, "blinded": true}, "human_critique": {"status": "not_run", "reviewer": null, "signed_at": null, "conflict_checked": false, "commentary": null}, "stages": [{"key": "target_materials", "status": "pending", "reason": null, "evidence": null}, {"key": "independent_readings", "status": "blocked", "reason": "The independent readings are incomplete or disagree; the source evidence must resolve the difference.", "evidence": {"provider_errors": []}}, {"key": "source_resolution", "status": "pending", "reason": null, "evidence": null}, {"key": "protocol_reconstruction", "status": "pending", "reason": null, "evidence": null}, {"key": "control_execution", "status": "pending", "reason": null, "evidence": null}, {"key": "control_comparison", "status": "pending", "reason": null, "evidence": null}, {"key": "publication", "status": "pending", "reason": null, "evidence": null}], "gaps": ["review.human_critique", "review.machine_critique.blocked"]}, "execution": {"state": "absent", "status": "not_run", "mode": null, "runs": [], "gaps": ["execution.not_run"]}, "provenance": {"entities": [{"id": "package:cd4449baf050a7824717b6c748cb63c7dcb84a7afcc4abb1398c34cb0d1cc172", "type": "sep_package", "label": "SEP v1 package for pmid:39647324"}], "activities": [{"id": "activity:conversion:pmid:39647324", "type": "conversion", "used": ["package:cd4449baf050a7824717b6c748cb63c7dcb84a7afcc4abb1398c34cb0d1cc172"], "agent": "agent:corpus-assay-engine"}], "agents": [{"id": "agent:minimax", "type": "model", "label": "minimax"}, {"id": "agent:minimax_alt", "type": "model", "label": "minimax_alt"}, {"id": "agent:corpus-assay-engine", "type": "software", "label": "Corpus assay engine"}], "source_run_id": "run-20261023T122449232913", "dsl_catalogue_fingerprint": "343fb30756ba6ec3", "capability_table_fingerprint": "2cb3e42f047d2ecf", "snapshot_id": "ba34b49490d9bfaf"}, "lineage": {"parent_id": "pmid:39647324", "parent_hash": "sha256:c9572ac552d553e297483013cf08b8fba167333c7cf7a8e5b53ac758ef8d41d0", "fork_of": null, "generation": 2}, "gaps": ["abstract", "asset:source:pmid:39647324 not verified", "authors", "capability", "corpus_record_absent", "execution.not_run", "method", "review.human_critique", "review.machine_critique.blocked", "step:obtain_source_data blocked on data:not_downloaded", "step:run_analysis blocked on no owned computational capability is bound to this experiment", "step:run_analysis input 'materials:the source data behind the published result in pmid:39647324' does not resolve to a declared asset", "targets"]}