For the purpose of building a dynamic user interface within an software application I wish to separate parts of a set of phrases which would be in the form of the examples below.
Examples:
- Customers who have never paid a dime.
- Vendors who are not very reliable.
- Products that are way too expensive.
Doing this is easy enough however I'm struggling for a term to describe the different parts of the sentence.
The first part perhaps would be the subject but what about the pronouns who or that (relative pronouns). Is there a phrase or term to describe the combination of the subject plus the relative pronoun that I could use as a single unit in discussion or documentation or am I better just to refer to it as something like a "customer pronoun pair" or "customer relative pronoun combination".
As far as the second part of the sentence (the non-bold parts in the examples above) I'm sure there must be a more common phrase but I could use some help in identifying what it is.
Another option perhaps would be to split the sentence into three parts to better describe the pieces but I'm not sure there is much value in it unless I could be convinced otherwise. My goal is to use these parts flexibly so that I can dynamically produce lists that appears something like the one below.
Customers who:
- have never paid a dime.
- are way too cheap.
- always pay on time.
Best Answer
Your question is somewhat misleading, and may contain a false assumption. A statement like the following:
is not a sentence. It's a noun phrase. Let's break that down:
Customers is a noun. Nouns are not inherently subjects or objects, so it's not correct to refer to this as either the subject or the object.
The remaining part who have never paid a dime is a relative clause, which is an embedded sentence that is used to modify something in the larger context. The subject of the embedded clause is the relative pronoun who, and the remainder have never paid a dime is the predicate of the relative clause.
However, using terms such as "predicate" and "relative clause" may be intimidating to people using your software. My best offering for newbie-friendly terminology would be: