Triple
T28616286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WaitForSingleObject |
E724279
|
entity |
| Predicate | multiObjectWaitSupport |
P136126
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [WaitForSingleObject, multiObjectWaitSupport, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: multiObjectWaitSupport Context triple: [WaitForSingleObject, multiObjectWaitSupport, false]
-
A.
supportsMultipleObjects
chosen
Indicates that the relationship or action can simultaneously involve or apply to more than one object at the same time.
-
B.
mayBeHeldConcurrentlyWith
Indicates that one event, state, or condition is allowed to occur or be in effect at the same time as another without conflict or violation of constraints.
-
C.
waitsArePerformedBy
Indicates that instances of waiting are carried out or executed by a particular agent or entity.
-
D.
supportsDistributedObjects
Indicates that one entity provides the capability to create, manage, or interact with objects whose state and behavior are distributed across multiple networked locations.
-
E.
multipleWorkingWith
Indicates that an entity is simultaneously collaborating or engaged in work with more than one other entity.
- 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.