Triple
T28616299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WaitForSingleObject |
E724279
|
entity |
| Predicate | synchronizationScope |
P61547
|
FINISHED |
| Object | single waitable object |
—
|
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: single waitable object | Statement: [WaitForSingleObject, synchronizationScope, single waitable object]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: synchronizationScope Context triple: [WaitForSingleObject, synchronizationScope, single waitable object]
-
A.
syncScope
chosen
Indicates that two or more processes, threads, or operations are coordinated to occur within the same synchronization context or boundary.
-
B.
synchronizationBoundary
Indicates a point or condition at which concurrent or distributed processes must align or coordinate their states or actions to maintain consistency.
-
C.
synchronizationArea
Indicates that two or more processes, components, or entities share a common region or scope within which their activities are coordinated or synchronized.
-
D.
synchronizationRole
Indicates the specific function or responsibility an entity has within a synchronization process or coordination relationship with other entities.
-
E.
synchronizationTrigger
Indicates that one process, event, or condition initiates or controls the timing of another so they occur in a coordinated or synchronized manner.
- 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_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 4:32 a.m.