Triple
T8610246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Service Worker |
E203897
|
entity |
| Predicate | runsInContext |
P50547
|
FINISHED |
| Object | Web browser |
—
|
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: Web browser | Statement: [Service Worker, runsInContext, Web browser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsInContext Context triple: [Service Worker, runsInContext, Web browser]
-
A.
runsUnder
Indicates that one process, task, or component operates within the control, environment, or context provided by another system, platform, or framework.
-
B.
runsWith
Indicates that one entity runs together alongside another entity, typically at the same time and place.
-
C.
runsOutsideProcess
Indicates that an operation or task is executed in a separate, external process rather than within the main process.
-
D.
executedIn
chosen
Indicates that an action or process is carried out or takes place within a specified location, context, or environment.
-
E.
runsFrom
Indicates that one entity flees or escapes away from another entity.
- 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.