This HTML5 document contains 9 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

PrefixNamespace IRI
dctermshttp://purl.org/dc/terms/
n10http://dbkwik.webdatacommons.org/resource/9O-gtAxhYZxHMOD3X7qJfw==
n3http://dbkwik.webdatacommons.org/ontology/
n2http://dbkwik.webdatacommons.org/resource/-VtCAxe_6DZUdSc4pZx10A==
n5http://dbkwik.webdatacommons.org/resource/yK_SSGKEu3CtUKTDtVMHNg==
rdfshttp://www.w3.org/2000/01/rdf-schema#
n11http://dbkwik.webdatacommons.org/resource/LvJ1TZdDI5QfvlTELwszTQ==
n8http://dbkwik.webdatacommons.org/resource/0ogyGJoKAah4ARjyy99ulA==
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n9http://dbkwik.webdatacommons.org/resource/2GlM1kjX2_9DZCmMXzPDfA==
n7http://dbkwik.webdatacommons.org/resource/Awcxbj8lGh8enh3DO_ufjg==
xsdhhttp://www.w3.org/2001/XMLSchema#
Subject Item
n2:
rdfs:label
Sickle Weasel (Beyblade)
rdfs:comment
The beyblade often appeared in a swirling vortex, and had the ability to appear and disappear. It was highly implied that the attack-ring was very sharp, as it sliced easily through bamboo. It was likely an attack or speed class beyblade. However, as was the problem with many Zagart Industries-made beyblades, it was very delicate, and easily shattered. Sickle Weasel ended up sheared in half by Dranzer.
dcterms:subject
n5: n7: n8: n9: n10: n11:
n3:abstract
The beyblade often appeared in a swirling vortex, and had the ability to appear and disappear. It was highly implied that the attack-ring was very sharp, as it sliced easily through bamboo. It was likely an attack or speed class beyblade. However, as was the problem with many Zagart Industries-made beyblades, it was very delicate, and easily shattered. Sickle Weasel ended up sheared in half by Dranzer.