Triple
T26992215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cilk |
E679886
|
entity |
| Predicate | schedulingPolicy |
P128506
|
FINISHED |
| Object | randomized work stealing |
—
|
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: randomized work stealing | Statement: [Cilk, schedulingPolicy, randomized work stealing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: schedulingPolicy Context triple: [Cilk, schedulingPolicy, randomized work stealing]
-
A.
schedulingStrategy
chosen
Indicates how tasks, events, or operations are ordered and allocated over time or resources relative to one another.
-
B.
schedulingRule
Indicates a rule or constraint that governs when, how, or under what conditions an event or task may be scheduled.
-
C.
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.
-
D.
planningPolicy
Indicates that one entity establishes or defines rules, guidelines, or strategies governing how another entity should plan or make planning-related decisions.
-
E.
ordinationPolicy
Indicates the rules or criteria governing how entities are ordered, ranked, or arranged relative to one another.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621915ee48190b508025afa2fb4fc |
completed | May 2, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 6:52 a.m.