Triple
T17674845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BEAM virtual machine |
E440619
|
entity |
| Predicate | schedulingStrategy |
P128506
|
FINISHED |
| Object | preemptive |
—
|
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: preemptive | Statement: [BEAM virtual machine, schedulingStrategy, preemptive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: schedulingStrategy Context triple: [BEAM virtual machine, schedulingStrategy, preemptive]
-
A.
schedulingRule
Indicates a rule or constraint that governs when, how, or under what conditions an event or task may be scheduled.
-
B.
schedulingUnit
Indicates a relationship where one entity functions as a unit or block used for organizing, allocating, or managing time or resources in a schedule.
-
C.
usedForScheduling
Indicates that something is employed to plan, arrange, or coordinate the timing of events, tasks, or activities.
-
D.
usedInSchedulingSystems
Indicates that something is employed as a component or mechanism within scheduling systems to plan, allocate, or manage tasks, resources, or time.
-
E.
blockAllocationStrategy
Indicates how blocks are chosen, sized, or arranged when allocating storage or memory resources.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f6ba22081909e2099490c047378 |
completed | April 19, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 10 a.m.