Define the claim before counting links
NIST’s Generative AI Profile recommends checking sources and citations and describes provenance as information about origin and history. The dependency exercise here is an original way to make those checks visible. It does not assign a probability of truth from a citation count or treat provenance as a guarantee that a source is correct.
Use two separate fictional claims: C1 says a facility has stated capacity of 100 units for a specified period; C2 says it actually produced 100 units in that period. Capacity and realized output are different quantities. A source supporting C1 does not establish C2 merely because both statements contain the number 100.
Trace an original three-report dependency chain
Assume an invented primary disclosure F0 states capacity of 100 units and says nothing about actual output. Report R1 cites F0 but changes the wording to produced 100 units. Report R2 cites R1. Report R3 summarizes R1 and R2. These are unnamed teaching documents, not allegations about real publishers.
The completed dependency record reads: R1 depends on F0; R2 depends on R1; R3 depends on R1 and R2. All three reports therefore share one upstream branch. Their agreement on production can arise from the wording change in R1. Neither an additional URL nor fresh prose creates an independent production measurement.
Complete support statuses for both claims
For C1, record F0 as a source for stated capacity, subject to checking its date, scope and definitions. For C2, record unsupported by the documents inspected: the available upstream disclosure concerns capacity. Do not write disproved solely because the inspected source lacks a production figure; the actual output remains unknown in this first document set.
The record should retain the exact claim, unit, period, source passage and dependency path. A copied source can still convey a correct fact, and a primary source can contain errors. The aim is to avoid counting the same evidentiary origin repeatedly, not to reject all summaries or declare an original document infallible.
Add a distinct observation and update only what it supports
Now stipulate an independently originated operating log F1 for the same facility and period, with verified compatible definitions, showing actual output of 85 units. The revised teaching record supports stated capacity of 100 from F0 and actual output of 85 from F1. Under those compatibility assumptions, output divided by capacity is 85 / 100 = 85%.
This new branch supplies information that counting R1, R2 and R3 could not. If period or unit compatibility were unresolved, the 85% calculation would also remain unresolved. It is not a measured utilization rate for a real business. Likewise, separate AI answers or a separate AI checking pass do not automatically supply independent underlying evidence or qualified human expertise.
Method, sources, and limits
The documents, graph and numbers are original hypothetical teaching inputs checked on 27 October 2026. The source profile supports verification and provenance principles, not the invented production facts. AI assisted this draft; separate AI verification is required before publication and is not qualified human financial review. No actual publisher, business or investment thesis was evaluated.
Sources & checking dates
Primary references checked for this guide. A source supports the claim attributed to it; it does not endorse Thesis Lab or validate an example's investment outcome.
- NIST AI 600-1: Generative Artificial Intelligence Profile, MS-2.5-003 and content provenance ↗Checked 2026-10-27
Educational examples are hypothetical unless explicitly identified as a dated source observation. Product details can change after the update date.