Triple
T28616832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WSAAsyncSelect |
E724290
|
entity |
| Predicate | controlsSocket |
P101813
|
FINISHED |
| Object | 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: nonblocking mode | Statement: [WSAAsyncSelect, controlsSocket, nonblocking mode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlsSocket Context triple: [WSAAsyncSelect, controlsSocket, nonblocking mode]
-
A.
controlLink
chosen
Indicates a relationship where one entity exerts control, influence, or governing authority over another entity or process.
-
B.
controlProtocol
Indicates that one entity governs, regulates, or coordinates the behavior or operations of another according to a defined set of rules or procedures.
-
C.
exportControl
Indicates that an entity is subject to rules or restrictions governing the transfer or export of goods, services, or information across borders.
-
D.
controlsSystem
Indicates that one entity has the authority or capability to direct, manage, or regulate the operation of a system.
-
E.
controlStand
Indicates that one entity manages, directs, or regulates the operation or behavior of another entity or system.
- 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_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 28, 2026, 4:32 a.m.