Triple
T10329398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Push API |
E242837
|
entity |
| Predicate | exposesEvent |
P93441
|
FINISHED |
| Object | push event in service workers |
—
|
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: push event in service workers | Statement: [Push API, exposesEvent, push event in service workers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exposesEvent Context triple: [Push API, exposesEvent, push event in service workers]
-
A.
introducedEvent
Indicates that an entity is responsible for bringing an event into existence or initiating it for the first time.
-
B.
hasSideEvent
Indicates that an event is associated with an additional, related side event occurring alongside it.
-
C.
observedEvent
Indicates that an entity has perceived, detected, or recorded the occurrence of a particular event.
-
D.
coversEvent
Indicates that one event includes, spans, or encompasses the time period or occurrence of another event.
-
E.
eventTarget
Indicates that an event is directed toward, affects, or is intended for a particular target entity.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7cfd54c8190b6f88598339536d1 |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f760e88190abea6dcc4f04f2c1 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d7cada7881908beba55a1dc9ecb9 |
completed | April 7, 2026, 10:09 a.m. |
Created at: April 6, 2026, 11:52 a.m.