Triple
T28616821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WSAAsyncSelect |
E724290
|
entity |
| Predicate | notificationMechanism |
P7414
|
FINISHED |
| Object | Windows message queue |
—
|
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: Windows message queue | Statement: [WSAAsyncSelect, notificationMechanism, Windows message queue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notificationMechanism Context triple: [WSAAsyncSelect, notificationMechanism, Windows message queue]
-
A.
notificationType
Indicates the specific category or kind of notification associated with an event or action.
-
B.
notification
Indicates that one entity sends or presents an alert or message to another entity to inform them of some event, change, or required action.
-
C.
alertMethod
chosen
Indicates the method or channel through which an alert or notification is delivered from a source to a recipient.
-
D.
requiresNotification
Indicates that a particular action, event, or state must trigger a notification to be sent to relevant parties.
-
E.
followUpMechanism
Indicates a mechanism or process that is used to continue, monitor, or respond to a prior action, event, or communication.
- 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_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 4:32 a.m.