Triple
T28616332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WaitForMultipleObjects |
E724280
|
entity |
| Predicate | supportsAlertableWait |
P164935
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [WaitForMultipleObjects, supportsAlertableWait, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAlertableWait Context triple: [WaitForMultipleObjects, supportsAlertableWait, no]
-
A.
alertableWait
chosen
Indicates that one entity waits for another or for a condition to be met in a way that can be interrupted or awakened by alerts, signals, or events.
-
B.
canWaitFor
Indicates that one entity is able or permitted to delay action or progress until another specified entity or event occurs.
-
C.
waitsArePerformedBy
Indicates that instances of waiting are carried out or executed by a particular agent or entity.
-
D.
canBeSignaledBy
Indicates that one entity is capable of being triggered, notified, or activated by another entity through some form of signaling.
-
E.
supportsCooperativeScheduling
Indicates that one entity provides or enables cooperative scheduling capabilities for another entity or process.
- 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_6a0164b052608190adc93240dad50a06 |
completed | May 11, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_6a01637fd3ac8190970eb09650d1e659 |
completed | May 11, 2026, 5:05 a.m. |
Created at: April 28, 2026, 4:32 a.m.