Prompt 3.8.1, single pass. Source: NCT04004988_soa.pdf (PDF pages 1-3 = document pages 9-11 per PAGEMAP.md). No protocol markdown available.
| # | where | call made | alternative | detail |
|---|---|---|---|---|
| D1 | p.11, general note "If multiple procedures take place at the same time point..." (marker g2) | Kept as one table-wide note, anchored to header row 1 for traceability only | Bind the note to the seven activities it names (Safety 12-lead ECG, Supine Vital Signs, PK Sampling, Clinical Laboratory Tests, Immunogenicity, Blood glucose monitoring, Pharmacogenetic Sample) | 4 |
| D2 | p.10, header row 2 | Row named "Study Day" (synthesised); the printed "Procedure" in its label cell is read as the heading of the activity-name column | Use the printed "Procedure" as the property name | 3 |
| D3 | p.10, header row 1, column 15 ("ED^c") | ED recorded as a value of the Epoch row, with an empty study-day cell below | Treat ED as a visit (early-discontinuation visit) rather than an epoch value | 3 |
continuation. Header rows were de-duplicated.main_soa. Periods 1 and 2 share one printed day grid for the same participants (a crossover), so they were not split into tracks.footnote annotations with synthesised markers n1-n12, each bound to its own row (method: synthesized).footnote rather than source_note. n10 contains Section 9.4.6 and 9.7 references inside explanatory text, so it stays a footnote.Table 1: "Study Schedule Protocol I8F-MC-GPGS"
- Type main_soa, document pages 10-11.
- 14 data columns (2-15): D-28 to D-2, D-1, D1, D2, D3, D4, D5, D6, D7, D8, D15, D21, D36 (±1), ED.
- 2 header rows and 20 activity rows (rows 3-22). The table is flat: every row is a level-0 activity with marks (indentation_method: assumed_flat).
- Activity rows per page:
- p.10: 17 rows (rows 3-19).
- p.11: 3 rows (rows 20-22).
- p.9: 0 rows. It is outside the declared range: it carries only the section heading "2. Schedule of Activities", with no table content.
- 280 activity_schedule cells, 90 of them non-empty.
- Cell values that are timing text rather than marks were transcribed literally: "0 hour", "Predose", "Predose, 12", "Predose, 8, 12", "24, 36", and the hour values 24/48/72/96/120/144/168/336/480. They were not split or converted to X.
schedule_property location on row 1 with method: synthesized, following the §6 table-scope convention. The marker is deliberately not placed on any element's annotation_markers.pdftotext -bbox on pages 10-11.-layout text dump it appeared shifted left, and the bbox check confirms D15.None. Every annotation has at least one marker location, and every marker is defined in the source.
indentation_method: assumed_flat on all 20 activities.method: synthesized on the marker locations of n1-n12 (activity_name), and of g1 and g2 (schedule_property row 1).unresolved locations.