Triple
T8610273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Service Worker |
E203897
|
entity |
| Predicate | registeredVia |
P55783
|
FINISHED |
| Object | navigator.serviceWorker.register() |
—
|
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: navigator.serviceWorker.register() | Statement: [Service Worker, registeredVia, navigator.serviceWorker.register()]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registeredVia Context triple: [Service Worker, registeredVia, navigator.serviceWorker.register()]
-
A.
registrationStatus
Indicates the current state or condition of an entity’s enrollment or registration within a given system or process.
-
B.
registrationMode
Indicates the method or process by which something is registered or enrolled.
-
C.
inscriptionStatus
Indicates the current state or condition of an inscription, such as whether it has been created, verified, updated, or removed.
-
D.
membershipOrigin
Indicates the source or basis from which an entity’s membership in a group, organization, or category is derived.
-
E.
establishedThrough
chosen
Indicates that a relationship, structure, or state comes into existence or is formally created by means of a specified process, action, or intermediary.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46ee96ac8190809817c403da2889 |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:25 p.m.