Triple
T28771686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WSAEventSelect |
E726427
|
entity |
| Predicate | changesStateOf |
P123358
|
FINISHED |
| Object | socket to nonblocking mode |
—
|
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: socket to nonblocking mode | Statement: [WSAEventSelect, changesStateOf, socket to nonblocking mode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changesStateOf Context triple: [WSAEventSelect, changesStateOf, socket to nonblocking mode]
-
A.
changedFrom
Indicates that an entity previously had one state, value, or form and was altered or updated from that prior condition to a new one.
-
B.
transitionState
chosen
Indicates a change in condition or phase from one defined state to another within a process or system.
-
C.
changesProperty
Indicates that one entity causes a change in a specific property or attribute of another entity.
-
D.
changedUnder
Indicates that one entity has undergone alteration, modification, or transformation as a result of the influence, action, or conditions imposed by another entity.
-
E.
mayChangeTo
Indicates that one state, condition, or value is allowed or able to transition into another.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:16 a.m.