Triple
T8610290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Service Worker |
E203897
|
entity |
| Predicate | originPolicy |
P83866
|
FINISHED |
| Object | Same-origin policy applies |
—
|
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: Same-origin policy applies | Statement: [Service Worker, originPolicy, Same-origin policy applies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originPolicy Context triple: [Service Worker, originPolicy, Same-origin policy applies]
-
A.
originProtectedStatus
Indicates that an entity’s original source or location is subject to protection, restriction, or special safeguarding status.
-
B.
eraPolicy
Indicates that a specific policy was in effect during a particular historical or temporal era.
-
C.
referencePolicy
Indicates that one entity defines rules or guidelines governing how another entity may be referred to, cited, or mentioned.
-
D.
locationPolicy
Indicates a rule or constraint governing where an entity is allowed, required, or restricted to be located.
-
E.
originUse
Indicates that one entity is used as the original source, basis, or starting point for the creation, derivation, or use of another 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_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. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:25 p.m.