Triple
T28616263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WaitForSingleObject |
E724279
|
entity |
| Predicate | timeoutUnit |
P156885
|
FINISHED |
| Object | milliseconds |
—
|
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: milliseconds | Statement: [WaitForSingleObject, timeoutUnit, milliseconds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeoutUnit Context triple: [WaitForSingleObject, timeoutUnit, milliseconds]
-
A.
timeoutDuration
Indicates the length of time that may elapse before an operation, request, or session is automatically terminated or considered failed.
-
B.
timeoutRule
Indicates a rule that defines when and under what conditions an operation, request, or process should automatically time out.
-
C.
timeoutAllocation
Indicates the assignment or distribution of a specific time limit or timeout duration to an operation, resource, or process.
-
D.
timeUnitOf
chosen
Indicates that one entity specifies the unit of time (e.g., seconds, minutes, hours) in which the other entity’s temporal quantity or duration is expressed.
-
E.
timeLimited
Indicates that the relationship or action is constrained to occur or remain valid only within a specific, limited time period.
- 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_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 28, 2026, 4:32 a.m.