Triple
T28616957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WSARecvFrom |
E724293
|
entity |
| Predicate | declaredInLibrary |
P166231
|
FINISHED |
| Object | Ws2_32.lib |
—
|
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: Ws2_32.lib | Statement: [WSARecvFrom, declaredInLibrary, Ws2_32.lib]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declaredInLibrary Context triple: [WSARecvFrom, declaredInLibrary, Ws2_32.lib]
-
A.
implementedInLibrary
Indicates that a particular functionality, feature, or component is realized and provided within a specific software library.
-
B.
declaredInDocument
Indicates that something (such as an entity, concept, or statement) is formally specified or announced within a particular document.
-
C.
declaredWith
Indicates that one entity is formally specified, introduced, or defined in association with another entity (such as a context, modifier, or accompanying element) at the point of its declaration.
-
D.
declaredBy
Indicates that something (such as a statement, variable, or entity) is formally introduced, specified, or announced by a particular agent or source.
-
E.
declaredFrom
Indicates that one entity is formally announced, stated, or proclaimed by another as its source or origin.
- 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_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 4:32 a.m.