Triple
T28615962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HeapAlloc |
E724272
|
entity |
| Predicate | allocationGranularity |
P166493
|
FINISHED |
| Object | bytes as requested in dwBytes |
—
|
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: bytes as requested in dwBytes | Statement: [HeapAlloc, allocationGranularity, bytes as requested in dwBytes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allocationGranularity Context triple: [HeapAlloc, allocationGranularity, bytes as requested in dwBytes]
-
A.
scalingGranularity
Indicates the level of detail or resolution at which a quantity, process, or system is adjusted or scaled.
-
B.
executionGranularity
Indicates the level of detail or subdivision at which an operation, task, or process is carried out or controlled.
-
C.
controlGranularity
Indicates the level of detail or fineness with which control or regulation is applied within a given process or system.
-
D.
accessGranularity
Indicates the level of detail or scope at which access or permissions are defined and applied within a system or resource.
-
E.
allocationShare
Indicates the proportion or portion of a total resource, amount, or benefit that is assigned to a particular entity within an allocation.
- F. None of above. chosen
Provenance (4 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_69f6622808b48190bbabcc75288ab031 |
completed | May 2, 2026, 8:44 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f6617a7e7c81908cfac4a2250797ee |
completed | May 2, 2026, 8:41 p.m. |
Created at: April 28, 2026, 4:31 a.m.