Triple
T28616994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WSARecvFrom |
E724293
|
entity |
| Predicate | applicableSocketState |
P29735
|
FINISHED |
| Object | bound |
—
|
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: bound | Statement: [WSARecvFrom, applicableSocketState, bound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: applicableSocketState Context triple: [WSARecvFrom, applicableSocketState, bound]
-
A.
hasSocket
Indicates that one entity is equipped with or provides a socket or receptacle for another entity to connect to or plug into.
-
B.
isStateSupported
chosen
Indicates that a particular state or condition is recognized, allowed, or handled within a given system or context.
-
C.
connectsState
Indicates a relationship where one entity serves as a link or conduit between different states, conditions, or statuses of another entity.
-
D.
activeInState
Indicates that an entity is currently functioning, operating, or valid within a specified state or condition.
-
E.
acceptsStateOn
Indicates that an entity agrees to or is configured to receive and handle a specified state or status from another entity or process.
- 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_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: April 28, 2026, 4:32 a.m.