Triple
T28616853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WSAAsyncSelect |
E724290
|
entity |
| Predicate | cancelsEventsWhen |
P70879
|
FINISHED |
| Object | lEvent is set to 0 |
—
|
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: lEvent is set to 0 | Statement: [WSAAsyncSelect, cancelsEventsWhen, lEvent is set to 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cancelsEventsWhen Context triple: [WSAAsyncSelect, cancelsEventsWhen, lEvent is set to 0]
-
A.
alsoCanceledEvent
Indicates that one event was canceled in addition to, or along with, another specified event.
-
B.
cancels
chosen
Indicates that one entity invalidates, nullifies, or stops the effect, operation, or scheduled occurrence of another entity or action.
-
C.
endUseEvent
Indicates an event marking the final or terminating use of something by an entity.
-
D.
canceledAfter
Indicates that one event or action was canceled at a point in time occurring after another specified event or action.
-
E.
canceledBefore
Indicates that one event, reservation, or commitment was canceled at a time earlier than another specified event or reference point.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:32 a.m.