RFC 3986
E453731
RFC 3986 is the Internet standard that defines the syntax and semantics of Uniform Resource Identifiers (URIs), superseding earlier URI specifications.
All labels observed (6)
| Label | Occurrences |
|---|---|
| Uniform Resource Identifier | 3 |
| RFC 3986 canonical | 2 |
| URI design in Internet protocols | 1 |
| URI syntax and semantics | 1 |
| Uniform Resource Identifier (URI): Generic Syntax | 1 |
| Uniform Resource Identifiers | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T4575435 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 3986 Context triple: [UTF-7, deprecatedIn, RFC 3986]
-
A.
RFC 2068
RFC 2068 is an early Internet standards document that specifies the HTTP/1.1 protocol, detailing its methods, headers, and overall message structure for web communication.
-
B.
RFC 2616
RFC 2616 is the IETF specification that defined HTTP/1.1, standardizing the core semantics and behavior of the Hypertext Transfer Protocol used on the web.
-
C.
RFC 7234
RFC 7234 is an IETF specification that defines HTTP/1.1 caching semantics, including how responses may be stored, reused, and validated by caches.
-
D.
RFC 9110
RFC 9110 is an IETF specification that defines the core semantics and architecture of the Hypertext Transfer Protocol (HTTP).
-
E.
RFC 4627
RFC 4627 is the original IETF specification that formally defined the JSON (JavaScript Object Notation) data interchange format.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 3986 Target entity description: RFC 3986 is the Internet standard that defines the syntax and semantics of Uniform Resource Identifiers (URIs), superseding earlier URI specifications.
-
A.
RFC 2068
RFC 2068 is an early Internet standards document that specifies the HTTP/1.1 protocol, detailing its methods, headers, and overall message structure for web communication.
-
B.
RFC 2616
RFC 2616 is the IETF specification that defined HTTP/1.1, standardizing the core semantics and behavior of the Hypertext Transfer Protocol used on the web.
-
C.
RFC 7234
RFC 7234 is an IETF specification that defines HTTP/1.1 caching semantics, including how responses may be stored, reused, and validated by caches.
-
D.
RFC 9110
RFC 9110 is an IETF specification that defines the core semantics and architecture of the Hypertext Transfer Protocol (HTTP).
-
E.
RFC 4627
RFC 4627 is the original IETF specification that formally defined the JSON (JavaScript Object Notation) data interchange format.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ URI specification ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines |
URI components
ⓘ
URI generic syntax ⓘ URI normalization ⓘ URI reference ⓘ URI resolution ⓘ URI scheme name syntax ⓘ URI semantics ⓘ Uniform Resource Identifier ⓘ absolute URI ⓘ generic URI syntax independent of scheme ⓘ hierarchical URI ⓘ non-hierarchical URI ⓘ percent-encoding ⓘ relative reference ⓘ |
| definesABNF | URI syntax grammar ⓘ |
| definesComponent |
authority
ⓘ
fragment ⓘ host ⓘ path ⓘ port ⓘ query ⓘ scheme ⓘ userinfo ⓘ |
| hasURI | https://www.rfc-editor.org/rfc/rfc3986 ⓘ |
| intendedFor | Internet applications ⓘ |
| obsoletes |
RFC 2396
ⓘ
RFC 2732 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| publishedInSeries |
RFC
ⓘ
linked to:
RFCs
|
| relatedTo |
URL
ⓘ
URN ⓘ |
| RFCNumber | 3986 ⓘ |
| specifies |
URI comparison rules
ⓘ
relative resolution algorithm ⓘ reserved characters in URIs ⓘ unreserved characters in URIs ⓘ |
| standardizes |
URI semantics
ⓘ
URI syntax ⓘ |
| status | Internet Standard ⓘ |
| supersedes | earlier URI specifications ⓘ |
| title |
Uniform Resource Identifier (URI): Generic Syntax
ⓘ
linked to:
RFC 3986
|
| updates | URI syntax specifications ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: RFC 3986 Description of subject: RFC 3986 is the Internet standard that defines the syntax and semantics of Uniform Resource Identifiers (URIs), superseding earlier URI specifications.
Referenced by (9)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: RFC 3986
linked to: RFC 3986
linked to: RFC 3986
linked to: RFC 3986