Annotated samples for: I don’t think or I think … not – what is the difference?

Open data API in a single place

Provided by KU Leuven

Get early access to Annotated samples for: I don’t think or I think … not – what is the difference? API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2026.03.09 08:13
Created
2026.03.09
Available languages
English
Keywords
interactional device, epistemic modality, CTP-clause, rhetorical force, opinionative marker
Quality scoring

Dataset description

This dataset contains manually annotated random samples of the constructions I don’t think and I think … not, compiled for a study on neg-raising in English (Horn 1978; Nuyts 1990; Pichler 2013). The dataset was created to investigate the distribution and interpretation of neg-raising constructions and their relationship to epistemic stance marking in spoken English. The data were extracted from the British Spoken subcorpus of Collins WordbanksOnline, which consists of transcripts of spontaneous conversations and broadcast speech produced between 1972 and 2009 (Collins 2009). Queries were designed to retrieve tokens of I don’t think and I think, after which occurrences of not in the complement clause were manually identified to obtain tokens of I think … not. To ensure comparability between the constructions, no tense, modal or other variation of the matrix predicate was included in the search queries. Randomized samples of the retrieved tokens were manually examined and filtered to exclude irrelevant cases. The remaining tokens were manually annotated for the presence or absence of neg-raising and for relevant contextual properties in the surrounding discourse. This dataset may be used to replicate or extend research on neg-raising and the various semantic functions of CTP-clauses in spoken English.
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks