run-on (Q14992): Difference between revisions

From LexBib
(‎Removed claim: LexBib v2 legacy ID (P1): Q22232)
 
(12 intermediate revisions by 2 users not shown)
description / endescription / en
 
a term
Property / LexBib v2 legacy ID
 
Property / LexBib v2 legacy ID: Q22232 / rank
Normal rank
 
Property / LexBib v1 legacy ID: KipTerm_RunOn / reference
 
Property / skos:definition
 
a derivative, idiom, etc. placed at the end of an entry; a word or phrase not given separate headword status but added as a sub-entry under a word or phrase to which it is related. This is a typical treatment of derivatives that do not require separate definition; compare main entry.
Property / skos:definition: a derivative, idiom, etc. placed at the end of an entry; a word or phrase not given separate headword status but added as a sub-entry under a word or phrase to which it is related. This is a typical treatment of derivatives that do not require separate definition; compare main entry. / rank
 
Normal rank
Property / skos:definition: a derivative, idiom, etc. placed at the end of an entry; a word or phrase not given separate headword status but added as a sub-entry under a word or phrase to which it is related. This is a typical treatment of derivatives that do not require separate definition; compare main entry. / reference
 
Property / LexMeta OWL equivalent
 
Property / LexMeta OWL equivalent: http://w3id.org/meta-share/lexmeta/runOn / rank
 
Normal rank
Property / LexMeta OWL equivalent: http://w3id.org/meta-share/lexmeta/runOn / qualifier
 
Property / skos:inScheme
 
Property / skos:inScheme: Microstructure Feature / rank
 
Normal rank

Latest revision as of 20:23, 23 August 2023

a term
Language Label Description Also known as
English
run-on
a term

    Statements

    0 references
    0 references
    a derivative, idiom, etc. placed at the end of an entry; a word or phrase not given separate headword status but added as a sub-entry under a word or phrase to which it is related. This is a typical treatment of derivatives that do not require separate definition; compare main entry.