Triple
T34416003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Negation |
E883403
|
entity |
| Predicate | hasPragmaticEffect |
—
|
GENERATED |
| Object | can express denial |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPragmaticEffect Context triple: [Negation, hasPragmaticEffect, can express denial]
-
A.
pragmaticFunction
chosen
Indicates the role or purpose that an utterance or expression serves in context, such as its communicative intent or discourse function beyond literal meaning.
-
B.
hasEffectIn
Indicates that one entity produces, causes, or exerts an effect within a specified context, system, or environment.
-
C.
hasIntendedEffect
Indicates that one entity is expected or designed to produce a particular effect or outcome on another entity or context.
-
D.
hasDirectEffect
Indicates that one entity produces an immediate and unmediated impact or change on another entity.
-
E.
pragmaticStatus
Indicates the discourse or conversational role that an element plays in context, such as whether it is given, new, focused, or background information.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f349c2e3b88190a67834eb5bcffeaf |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:59 a.m.