RFC 4627
E208073
RFC 4627 is the original IETF specification that formally defined the JSON (JavaScript Object Notation) data interchange format.
All labels observed (2)
How this entity was disambiguated
This entity first appeared as the object of triple T1869660 — 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 4627 Context triple: [JSON, previouslyStandardizedAs, RFC 4627]
-
A.
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.
-
B.
RFC 7541
RFC 7541 is the IETF specification that defines the HPACK header compression format used by HTTP/2 to efficiently encode HTTP header fields.
-
C.
RFC 6840
RFC 6840 is an Internet Engineering Task Force (IETF) standards document that clarifies, updates, and consolidates the core specifications for the DNS Security Extensions (DNSSEC) protocol suite.
-
D.
RFC 7230
RFC 7230 is an IETF standard that specifies the core message syntax and routing semantics for the Hypertext Transfer Protocol (HTTP/1.1), including its use over secure transport like HTTPS.
-
E.
RFC 7233
RFC 7233 was an HTTP/1.1 specification that defined range requests and partial content delivery mechanisms for HTTP resources.
- 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 4627 Target entity description: RFC 4627 is the original IETF specification that formally defined the JSON (JavaScript Object Notation) data interchange format.
-
A.
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.
-
B.
RFC 7541
RFC 7541 is the IETF specification that defines the HPACK header compression format used by HTTP/2 to efficiently encode HTTP header fields.
-
C.
RFC 6840
RFC 6840 is an Internet Engineering Task Force (IETF) standards document that clarifies, updates, and consolidates the core specifications for the DNS Security Extensions (DNSSEC) protocol suite.
-
D.
RFC 7230
RFC 7230 is an IETF standard that specifies the core message syntax and routing semantics for the Hypertext Transfer Protocol (HTTP/1.1), including its use over secure transport like HTTPS.
-
E.
RFC 7233
RFC 7233 was an HTTP/1.1 specification that defined range requests and partial content delivery mechanisms for HTTP resources.
- F. None of above. chosen
Statements (45)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
technical specification ⓘ |
| area | Applications ⓘ |
| author | Douglas Crockford ⓘ |
| basedOn | JavaScript object literal notation subset ⓘ |
| category | Standards Track ⓘ |
| defines |
JSON array
ⓘ
JSON data interchange format ⓘ JSON false literal ⓘ JSON null literal ⓘ JSON number ⓘ JSON number format without octal or hex ⓘ JSON object ⓘ JSON string ⓘ JSON text ⓘ JSON true literal ⓘ JSON whitespace handling ⓘ MIME registration for application/json ⓘ application/json media type ⓘ |
| definesCharacterEncoding |
UTF-16
ⓘ
UTF-32 ⓘ UTF-8 ⓘ |
| definesEscapingRulesFor | JSON strings ⓘ |
| definesTopLevelType | JSON text must be either object or array ⓘ |
| documentType | Internet Standards Track specification ⓘ |
| intendedAudience |
Internet protocol designers
ⓘ
application developers ⓘ |
| language | English ⓘ |
| mediaType | application/json ⓘ |
| obsoletedBy |
RFC 7158
ⓘ
RFC 7159 ⓘ
linked to:
RFC 8259
RFC 8259 ⓘ |
| primaryUse |
data interchange
ⓘ
structured data representation ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| publishedInSeries |
Request for Comments
ⓘ
linked to:
RFCs
|
| relation | Original IETF specification for JSON ⓘ |
| rfcNumber | 4627 ⓘ |
| specifiesSyntaxFor |
JSON
ⓘ
JavaScript Object Notation ⓘ
linked to:
JSON
|
| standardizes | JSON data format ⓘ |
| status | Obsoleted ⓘ |
| title | The application/json Media Type for JavaScript Object Notation (JSON) ⓘ |
| workingGroup | IETF JSON specification effort ⓘ |
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 4627 Description of subject: RFC 4627 is the original IETF specification that formally defined the JSON (JavaScript Object Notation) data interchange format.
Referenced by (5)
Full triples — surface form annotated when it differs from this entity's canonical label.