Triple
T10208188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTTP Strict Transport Security specification |
E242258
|
entity |
| Predicate | standardizedIn |
P7508
|
FINISHED |
| Object |
RFC 6797
RFC 6797 is the Internet Engineering Task Force (IETF) document that defines the HTTP Strict Transport Security (HSTS) mechanism for enforcing secure HTTPS connections in web browsers.
|
E849481
|
NE FINISHED |
How this triple was built (4 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: RFC 6797 | Statement: [HTTP Strict Transport Security specification, standardizedIn, RFC 6797]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 6797 Context triple: [HTTP Strict Transport Security specification, standardizedIn, RFC 6797]
-
A.
RFC 7127
RFC 7127 is an Internet Engineering Task Force (IETF) document that specifies procedures and guidelines related to the IETF standards process.
-
B.
RFC 7519
RFC 7519 is the Internet standard that specifies the JSON Web Token (JWT) format for securely representing claims between parties in web authentication and authorization.
-
C.
RFC 6749
RFC 6749 is the IETF specification that defines the OAuth 2.0 authorization framework used for secure delegated access to web resources.
-
D.
RFC 6437
RFC 6437 is an Internet Engineering Task Force (IETF) specification that originally defined the IPv6 flow label behavior and usage before being superseded by RFC 8999.
-
E.
RFC 6750
RFC 6750 is an IETF specification that defines the use of bearer tokens for securing HTTP requests in the OAuth 2.0 authorization framework.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: RFC 6797 Triple: [HTTP Strict Transport Security specification, standardizedIn, RFC 6797]
Generated description
RFC 6797 is the Internet Engineering Task Force (IETF) document that defines the HTTP Strict Transport Security (HSTS) mechanism for enforcing secure HTTPS connections in web browsers.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 6797 Target entity description: RFC 6797 is the Internet Engineering Task Force (IETF) document that defines the HTTP Strict Transport Security (HSTS) mechanism for enforcing secure HTTPS connections in web browsers.
-
A.
RFC 7127
RFC 7127 is an Internet Engineering Task Force (IETF) document that specifies procedures and guidelines related to the IETF standards process.
-
B.
RFC 7519
RFC 7519 is the Internet standard that specifies the JSON Web Token (JWT) format for securely representing claims between parties in web authentication and authorization.
-
C.
RFC 6749
RFC 6749 is the IETF specification that defines the OAuth 2.0 authorization framework used for secure delegated access to web resources.
-
D.
RFC 6437
RFC 6437 is an Internet Engineering Task Force (IETF) specification that originally defined the IPv6 flow label behavior and usage before being superseded by RFC 8999.
-
E.
RFC 6750
RFC 6750 is an IETF specification that defines the use of bearer tokens for securing HTTP requests in the OAuth 2.0 authorization framework.
- F. None of above. chosen
Provenance (5 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d395f8e2b881909c51f8210f09cd4f |
completed | April 6, 2026, 11:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d652c13d748190908d1869c60e84c3 |
completed | April 8, 2026, 1:06 p.m. |
| NEDg | Description generation | batch_69d653c9f3e48190a51f6c6285d55e1d |
completed | April 8, 2026, 1:10 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69d65433b62081908895b50139b3de3f |
completed | April 8, 2026, 1:12 p.m. |
Created at: April 6, 2026, 10:57 a.m.