Triple
T10208162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTTP Strict Transport Security specification |
E242258
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | HTTP header specification |
C23233
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: HTTP header specification Context triple: [HTTP Strict Transport Security specification, instanceOf, HTTP header specification]
-
A.
HTTP header field
An HTTP header field is a key-value pair in an HTTP message that conveys metadata and control information between a client and server, such as content type, caching policies, and authentication details.
-
B.
response header field
A response header field is a name-value pair in an HTTP response that conveys metadata about the response or the server’s handling of the request.
-
C.
W3C specification
A W3C specification is an official, collaboratively developed technical standard published by the World Wide Web Consortium that defines interoperable protocols, formats, and best practices for the World Wide Web.
-
D.
HTTP extension
chosen
An HTTP extension is an addition to the core HTTP protocol that introduces new headers, methods, or behaviors to support extra functionality while remaining compatible with existing HTTP infrastructure.
-
E.
DNS specification
A DNS specification defines the formal rules, data structures, and protocols governing how domain names are translated into IP addresses and other resource records across the internet.
- F. None of above.
Provenance (1 batch)
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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 10:57 a.m.