Is a constative always a complete sentence?

No. In context, a short answer such as “Tuesday” can state the requested information.

Can a false statement still be constative?

Yes. Whether it is true is a separate question from what speech act it performs.

Is this the same as an assertion in programming?

No. Programming assertions are executable checks or conditions; this term concerns communicative acts in language.

AI Glossary / Natural language and speech / Intermediate

Constative speech act

Definition

A constative speech act presents something as being the case, committing the speaker to a proposition in the relevant conversational sense. Statements, claims, confirmations and denials are examples in the taxonomy used by the source textbook.

What it means

When someone says “The meeting starts at noon,” they do more than produce a grammatical sentence: they put forward information about the meeting. The listener can accept it, challenge it or ask for evidence. The information may still be mistaken.

A denial is also a way of presenting a proposition, as in “The meeting does not start at noon.” What matters is the speaker's communicative commitment, not whether the sentence has a positive grammatical form.

Constative is a theory-dependent label. It has a history in speech-act theory and overlaps with categories called assertives or representatives in other classifications. This entry follows the practical dialogue taxonomy in Jurafsky and Martin rather than treating every historical use of the word as identical.

How it works

An interpreter examines what the utterance is doing in context. A declarative sentence often states something, but form and function can diverge. “You can close the window” may provide information about ability or permission, or indirectly suggest an action.

For dialogue annotation, the surrounding turns help determine whether the speaker is answering, confirming, denying or making a new claim. Different schemes divide these functions differently. DAMSL's statement category is a related operational treatment, not an exact replacement for every philosophical definition of constative.

For AI systems, it is useful to separate the act from the proposition's truth and source. A system can correctly identify that a customer asserted a fault while still lacking evidence that the fault occurred. Summaries should preserve attribution, uncertainty and negation rather than promote every reported statement into an independently verified fact.

Three practical examples

A meeting assistant records a participant's statement about a deadline while retaining who supplied the information.
A customer-support system distinguishes a denial of a fault from a request to repair one.
A dialogue analyst identifies when a speaker confirms an earlier interpretation instead of introducing a new topic.

Think of it this way

Think of placing a labeled claim on a shared discussion board. Others can use it, question it or replace it when new evidence arrives. The label identifies what is being put forward and by whom.

The analogy does not imply that every statement is a formal declaration or that putting it on the board makes it true. It illustrates conversational commitment to content.

Worked example

Separating a statement from a promise and a request

Consider three invented messages: “The report is in the shared folder,” “I will put the report in the shared folder,” and “Please put the report in the shared folder.”

In their straightforward readings, the first is a constative about the report's current location. The second is a commissive undertaking a future action. The third is a directive asking the listener to act. All mention the same report and folder, but they should produce different records.

For the first, a summary might store claim=report in folder and source=speaker. For the second, it might store a pending commitment with its actor. For the third, it might store a request awaiting a response. None of these alone proves a successful file upload.

Now add “I think” to the first message. The content remains a tentative statement, and the summary should preserve that uncertainty rather than silently making it definite.

Illustrative case study

A fictional project office uses an assistant to summarize status updates. An early version lists every mention of “uploaded” as completed work, including “I don't think the file was uploaded.” The office finds that a keyword-based view loses the speech act and negation.

Reviewers create examples of claims, denials, questions and commitments. They check whether the summary preserves the proposition, its source and any uncertainty. Where operational evidence matters, the assistant links the statement to a separate record of the actual file action if available.

The team does not discard conversational reports; they are useful evidence about what people communicated. It simply keeps them distinct from independently checked system events. The case is illustrative and reports no measured accuracy improvement.

Common misconceptions and mistakes

A constative is necessarily true. The category describes a communicative act, not truth verification.
Only positive statements qualify. Denials can also put forward content.
Every declarative sentence performs the same act. Context can support indirect requests or other functions.
Constative and commissive are interchangeable. One presents something as the case; the other undertakes a future action.
All taxonomies use the label identically. Historical and annotation frameworks differ.

Business use

Constative recognition can improve summaries, dialogue-state tracking and claim extraction. It helps distinguish what has been reported from what has been requested or promised. Preserve negation and uncertainty because those details can reverse the practical meaning of a status update.

A useful review process checks both the communicative label and the extracted content. If a customer says a delivery has not arrived, correctly tagging a statement is insufficient if the record drops not. Attribution also matters when multiple participants disagree about the same event.

Check your understanding

Why should “The report is available” and “I will make the report available” not be merged into one completed-task label?

Answer: The first states a present condition, while the second undertakes a future action. Even the present-condition statement remains a report unless supported by separate evidence.

Related terms

Speech act
Dialogue act
Negation
assertive
commissive
directive
proposition
attribution

Learn next

Read a dialogue-act annotation guide and compare it with the textbook's categories. Label a short fictional status exchange, separating propositions, requests and commitments, then check whether the final summary preserves each speaker's uncertainty.

Dialogue act

Sources

Jurafsky and Martin, Conversation and Its Structure: https://web.stanford.edu/~jurafsky/slp3/26.pdf. The constative category and related speech acts.

DAMSL Revised Manual, Statement: https://www.cs.rochester.edu/research/speech/damsl/RevisedManual/node7.html. Related practical annotation distinctions. The report-location examples and project-office case are original illustrations; the two taxonomies are not claimed to be identical.

Previous: Constant bitrate Next: Constellation model