Triple
T17568818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AnyCancellable |
E427883
|
entity |
| Predicate | cancelEffect |
P93429
|
FINISHED |
| Object | terminates the underlying subscription |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: terminates the underlying subscription | Statement: [AnyCancellable, cancelEffect, terminates the underlying subscription]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cancelEffect Context triple: [AnyCancellable, cancelEffect, terminates the underlying subscription]
-
A.
terminateEffect
chosen
Indicates that an ongoing effect, condition, or process is brought to an end or cancelled.
-
B.
cancels
Indicates that one entity invalidates, nullifies, or stops the effect, operation, or scheduled occurrence of another entity or action.
-
C.
cancelArgument
Indicates that one party withdraws, nullifies, or calls off a previously made argument or claim in relation to another entity.
-
D.
cancelPurpose
Indicates that one action, event, or entity serves to nullify, revoke, or terminate the intended purpose or effect of another.
-
E.
cancellation
Indicates that a previously planned or scheduled event, action, or agreement is being annulled, terminated, or rendered no longer valid.
- F. None of above.
Provenance (3 batches)
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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4592f29d08190bc3de905d35af849 |
completed | April 19, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fd7d048190b54ee4c6155612a5 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.