Triple
T28616835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WSAAsyncSelect |
E724290
|
entity |
| Predicate | eventMaskType |
P166884
|
FINISHED |
| Object | FD_READ |
—
|
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: FD_READ | Statement: [WSAAsyncSelect, eventMaskType, FD_READ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventMaskType Context triple: [WSAAsyncSelect, eventMaskType, FD_READ]
-
A.
eventLevel
Indicates the intensity, magnitude, or severity associated with an event within a defined scale or hierarchy.
-
B.
componentEventType
Indicates the type or category of event associated with a specific component.
-
C.
eventTypeCaptured
Indicates that the specific type or category of an event has been successfully recorded or logged.
-
D.
captureEvent
Indicates an event in which one entity successfully takes control, possession, or custody of another entity.
-
E.
accessibleForEventType
Indicates that something can be used, reached, or is available in the context of a specified type or category of event.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f664aa283c8190a869d0555eff60c6 |
completed | May 2, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f6645a615481909b53d94512ecbaf1 |
completed | May 2, 2026, 8:53 p.m. |
Created at: April 28, 2026, 4:32 a.m.