Triple
T27866956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CancellationToken |
E704380
|
entity |
| Predicate | cancellationRequestedIsIdempotent |
P164357
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [CancellationToken, cancellationRequestedIsIdempotent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cancellationRequestedIsIdempotent Context triple: [CancellationToken, cancellationRequestedIsIdempotent, true]
-
A.
cancellationAnnouncedOn
Indicates that the cancellation of something (e.g., an event, service, or agreement) was publicly announced on a specific date or time.
-
B.
canBeCancelled
Indicates that an action, event, or agreement is eligible to be terminated or revoked before completion.
-
C.
isCancelled
Indicates that a planned event, action, or arrangement has been officially terminated and will no longer take place.
-
D.
cancellationMethod
Indicates the method or process by which a previously arranged action, service, or agreement is canceled.
-
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. chosen
Provenance (4 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f644de4a84819087ddb84757fc4585 |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f643e818d481908fc66bc91bd25d77 |
completed | May 2, 2026, 6:35 p.m. |
Created at: April 27, 2026, 6:21 p.m.