declaration

Full identifier: http://purl.org/np/RAcIFSXjybW4MwcpnGyjgKBwAZVdZaVYFJFIeNYr4GuAk#declaration

Assigned to 1 class:

Minted in Nanopublication

 RAcIFSXjyb FIP-No-Choice-Declaration comment approve/disapprove edit as derived nanopublication

This is a local identifier minted within the nanopublication. http://purl.org/np/RAcIFSXjyb...#declaration declaration https://www.w3.org/ns/dcat#endDate endDate (this is a literal) "2050-12-31" .
This is a local identifier minted within the nanopublication. http://purl.org/np/RAcIFSXjyb...#declaration declaration https://www.w3.org/ns/dcat#startDate startDate (this is a literal) "2024-01-01" .
This is the identifier for this whole nanopublication. http://purl.org/np/RAcIFSXjyb... This nanopublication date and time when the nanopublication was created http://purl.org/dc/terms/created was created on (this is a literal) "2024-01-04T21:59:54Z" .

References

Nanopublication Part Subject Predicate Object Published By Published On
links a nanopublication to its assertion http://www.nanopub.org/nschema#hasAssertion assertion
declaration
FIP Wizard
2024-01-04T21:59:54.000Z
links a nanopublication to its assertion http://www.nanopub.org/nschema#hasAssertion assertion
declaration
FIP Wizard
2024-01-04T21:59:54.000Z
links a nanopublication to its assertion http://www.nanopub.org/nschema#hasAssertion assertion
declaration
2050-12-31
FIP Wizard
2024-01-04T21:59:54.000Z
links a nanopublication to its assertion http://www.nanopub.org/nschema#hasAssertion assertion
declaration
2024-01-01
FIP Wizard
2024-01-04T21:59:54.000Z
links a nanopublication to its assertion http://www.nanopub.org/nschema#hasAssertion assertion
declaration
FIP Wizard
2024-01-04T21:59:54.000Z
links a nanopublication to its assertion http://www.nanopub.org/nschema#hasAssertion assertion
declaration
Similar to metadata, benchmark submissions are given a number unique across MLCommons benchmarks. However, they are not resolvable by machines. The convention used is the benchmark round hyphenated with a unique submission number, e.g., 3.1-2000 for benchmark 3.1, first submission. Different benchmarks begin with different number spans, such as training begins at 2000 and HPC begins at 8000. It would be optimal if each benchmark and round had a PID.
FIP Wizard
2024-01-04T21:59:54.000Z

Raw

TriG(txt), JSON-LD(txt), N-Quads(txt), XML(txt)