Triple
T28616968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WSARecvFrom |
E724293
|
entity |
| Predicate | supportsIOMode |
P99857
|
FINISHED |
| Object | blocking |
—
|
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: blocking | Statement: [WSARecvFrom, supportsIOMode, blocking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsIOMode Context triple: [WSARecvFrom, supportsIOMode, blocking]
-
A.
supportsSeparateIOMode
Indicates that an entity is capable of operating with a distinct, independently managed input/output mode separate from its default or primary I/O behavior.
-
B.
supportedMode
chosen
Indicates that a system, device, or component is capable of operating in or handling a particular mode.
-
C.
doesNotSupportMode
Indicates that one entity lacks the capability or compatibility to operate in, or work with, a specified mode associated with another entity.
-
D.
hasPrimaryModeSupported
Indicates that an entity supports a particular mode as its main or default mode of operation.
-
E.
supportsModelType
Indicates that an entity is compatible with, or can operate using, a specified model type.
- 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_6a016ebba0448190b5319243e1b2feca |
completed | May 11, 2026, 5:52 a.m. |
| PD | Predicate disambiguation | batch_6a016d2486b4819085efe197ee21b707 |
completed | May 11, 2026, 5:46 a.m. |
Created at: April 28, 2026, 4:32 a.m.