Triple
T28616879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WSAWaitForMultipleEvents |
E724291
|
entity |
| Predicate | usesHandleType |
P54171
|
FINISHED |
| Object | WSAEVENT |
—
|
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: WSAEVENT | Statement: [WSAWaitForMultipleEvents, usesHandleType, WSAEVENT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHandleType Context triple: [WSAWaitForMultipleEvents, usesHandleType, WSAEVENT]
-
A.
usesHandle
Indicates that an entity operates, controls, or interacts with another entity by means of a handle or handled interface.
-
B.
hasHandleType
chosen
Indicates that one entity possesses or is characterized by a specific type or style of handle.
-
C.
usedWithType
Indicates that something is typically or appropriately used together with items of a specified type.
-
D.
usedToHandle
Indicates that one entity previously managed, processed, or dealt with another entity as part of its function or role.
-
E.
usedHandleOnPlatform
Indicates that an entity has used a particular handle (username) on a specified platform.
- 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_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:32 a.m.