Triple
T28616845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WSAAsyncSelect |
E724290
|
entity |
| Predicate | messagePosted |
P86788
|
FINISHED |
| Object | WM_USER-based application-defined message |
—
|
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: WM_USER-based application-defined message | Statement: [WSAAsyncSelect, messagePosted, WM_USER-based application-defined message]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: messagePosted Context triple: [WSAAsyncSelect, messagePosted, WM_USER-based application-defined message]
-
A.
postedTo
Indicates that one entity has submitted, shared, or published content to another entity, typically a platform, channel, or destination.
-
B.
postedIn
chosen
Indicates that a piece of content or message was submitted or shared within a particular forum, group, channel, or location.
-
C.
createdPost
Indicates that an entity authored or produced a specific post.
-
D.
messageSpace
Indicates a relationship where one entity provides or occupies a space or channel through which messages can be sent, stored, or exchanged between parties.
-
E.
laterPosting
Indicates that one posting, message, or publication occurs at a later time than another in a temporal sequence.
- 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_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:32 a.m.