Triple
T28616379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CreateSemaphore |
E724281
|
entity |
| Predicate | handleUsage |
P124801
|
FINISHED |
| Object | used with WaitForSingleObject |
—
|
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: used with WaitForSingleObject | Statement: [CreateSemaphore, handleUsage, used with WaitForSingleObject]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handleUsage Context triple: [CreateSemaphore, handleUsage, used with WaitForSingleObject]
-
A.
errorUsage
Indicates that an error has occurred in how something is used, invoked, or applied within a given context.
-
B.
respondUsage
Indicates that one entity replies or reacts in some manner to the use or application of another entity.
-
C.
hasUsageNote
Indicates that there is an associated explanatory note describing how or when something should be used.
-
D.
usesHandle
chosen
Indicates that an entity operates, controls, or interacts with another entity by means of a handle or handled interface.
-
E.
hasUsageRegister
Indicates that a linguistic expression is associated with a particular usage register or level of formality in communication.
- 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_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 4:32 a.m.