Triple
T28616335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WaitForMultipleObjects |
E724280
|
entity |
| Predicate | blockingBehavior |
P93412
|
FINISHED |
| Object | blocks calling thread until condition met or timeout |
—
|
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: blocks calling thread until condition met or timeout | Statement: [WaitForMultipleObjects, blockingBehavior, blocks calling thread until condition met or timeout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blockingBehavior Context triple: [WaitForMultipleObjects, blockingBehavior, blocks calling thread until condition met or timeout]
-
A.
limitBehavior
Indicates how an entity behaves or changes as it approaches a specified limit or boundary condition.
-
B.
lockBehavior
chosen
Indicates how an entity controls or restricts access, modification, or interaction with another entity through locking rules or mechanisms.
-
C.
unlockBehavior
Indicates that one entity enables access to or activates the behavior, functionality, or state of another entity.
-
D.
bootBehavior
Indicates how a system or device behaves during its startup or boot process.
-
E.
behaviorOnFirstHit
Indicates the specific response or outcome that occurs the first time a target or condition is successfully hit or triggered.
- 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.