Triple
T32414048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WebJobs |
E828295
|
entity |
| Predicate | resourceSharing |
P30619
|
FINISHED |
| Object | shares resources with hosting web app |
—
|
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: shares resources with hosting web app | Statement: [WebJobs, resourceSharing, shares resources with hosting web app]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resourceSharing Context triple: [WebJobs, resourceSharing, shares resources with hosting web app]
-
A.
sharesResourcesWith
chosen
Indicates that two entities mutually use, access, or allocate the same resources.
-
B.
sharesResourceType
Indicates that two or more entities use or are associated with the same type or category of resource.
-
C.
sharesSystemWith
Indicates that two entities operate within or are associated with the same overarching system or environment.
-
D.
sharesLibrariesWith
Indicates that two entities use or depend on at least one of the same libraries or library components.
-
E.
canBeShared
Indicates that something is capable of being distributed or accessed by multiple parties.
- 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.