Triple
T32414030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WebJobs |
E828295
|
entity |
| Predicate | triggeredJobBehavior |
P168702
|
FINISHED |
| Object | runs on demand or on schedule |
—
|
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: runs on demand or on schedule | Statement: [WebJobs, triggeredJobBehavior, runs on demand or on schedule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triggeredJobBehavior Context triple: [WebJobs, triggeredJobBehavior, runs on demand or on schedule]
-
A.
triggerStrategy
Indicates that one entity initiates or activates a particular strategy or plan in relation to another entity or context.
-
B.
executionTrigger
Indicates that one event, condition, or action initiates or causes the execution of another process or operation.
-
C.
triggerMethod
chosen
Indicates the method, mechanism, or procedure by which a particular event, action, or process is initiated or triggered.
-
D.
triggerCondition
Indicates the specific circumstances or state under which an associated event, action, or process is initiated or activated.
-
E.
triggeredFires
Indicates that one entity caused or initiated the occurrence of one or more fires in another entity or location.
- 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c25a81208190b108ab80ca851ff9 |
completed | May 3, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:53 a.m.