Triple
T10328368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Referrer Policy specification |
E242817
|
entity |
| Predicate | standardizes |
P1371
|
FINISHED |
| Object | Referrer-Policy HTTP header |
E242817
|
NE 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: Referrer-Policy HTTP header | Statement: [Referrer Policy specification, standardizes, Referrer-Policy HTTP header]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Referrer-Policy HTTP header Context triple: [Referrer Policy specification, standardizes, Referrer-Policy HTTP header]
-
A.
Referrer Policy specification
chosen
The Referrer Policy specification is a web standard that defines how much referrer information browsers include in requests to enhance privacy and security on the web.
-
B.
Location HTTP header
The Location HTTP header is a response header used by web servers to indicate the URL to which a client should be redirected or where a newly created resource can be found.
-
C.
RFC 7232
RFC 7232 is an HTTP/1.1 specification that defines conditional request mechanisms using validators like ETags and Last-Modified to support efficient caching and concurrency control on the web.
-
D.
RFC 7235
RFC 7235 is an IETF specification that defined the HTTP/1.1 authentication framework, including the use of challenge-response mechanisms like Basic and Digest authentication.
-
E.
HTTP Strict Transport Security specification
The HTTP Strict Transport Security specification is a web security standard that allows servers to enforce secure (HTTPS) connections by instructing browsers to refuse insecure HTTP access to a site.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7cf21e08190bf605daeea0d9dcf |
completed | April 7, 2026, 10:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d71db4a8dc81909adb2a044e74fd6b |
completed | April 9, 2026, 3:32 a.m. |
Created at: April 6, 2026, 11:52 a.m.