RFC 7158
E754585
RFC 7158 is an IETF specification that updates and clarifies the JSON (JavaScript Object Notation) data interchange format previously defined in RFC 4627.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 7158 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8755992 — 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 7158 Context triple: [RFC 4627, obsoletedBy, RFC 7158]
-
A.
RFC 7888
RFC 7888 is an Internet Engineering Task Force (IETF) standards document that refines and updates email-related protocols originally defined in RFC 6856.
-
B.
RFC 5838
RFC 5838 is an IETF specification that updates and extends OSPFv3 to support multiple address families, including IPv4 and IPv6, within a single protocol instance.
-
C.
RFC 7868
RFC 7868 is the IETF specification that documents and standardizes the Enhanced Interior Gateway Routing Protocol (EIGRP) as an informational routing protocol.
-
D.
RFC 5508
RFC 5508 is an Internet Engineering Task Force (IETF) standards document that specifies requirements and mechanisms related to IP networking, later refined and updated by RFC 6146.
-
E.
RFC 6587
RFC 6587 is an IETF standard that specifies the message framing and transmission of syslog messages over TCP.
- 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 7158 Target entity description: RFC 7158 is an IETF specification that updates and clarifies the JSON (JavaScript Object Notation) data interchange format previously defined in RFC 4627.
-
A.
RFC 7888
RFC 7888 is an Internet Engineering Task Force (IETF) standards document that refines and updates email-related protocols originally defined in RFC 6856.
-
B.
RFC 5838
RFC 5838 is an IETF specification that updates and extends OSPFv3 to support multiple address families, including IPv4 and IPv6, within a single protocol instance.
-
C.
RFC 7868
RFC 7868 is the IETF specification that documents and standardizes the Enhanced Interior Gateway Routing Protocol (EIGRP) as an informational routing protocol.
-
D.
RFC 5508
RFC 5508 is an Internet Engineering Task Force (IETF) standards document that specifies requirements and mechanisms related to IP networking, later refined and updated by RFC 6146.
-
E.
RFC 6587
RFC 6587 is an IETF standard that specifies the message framing and transmission of syslog messages over TCP.
- F. None of above. chosen
Statements (30)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
technical specification ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| clarifies |
JSON semantics
ⓘ
JSON syntax ⓘ |
| defines | JSON data interchange format ⓘ |
| focusesOn | JavaScript Object Notation NERFINISHED ⓘ |
| format | text ⓘ |
| intendedFor |
Internet protocols
ⓘ
data interchange ⓘ |
| language | English ⓘ |
| obsoletedBy |
RFC 7159
NERFINISHED
ⓘ
RFC 8259 NERFINISHED ⓘ |
| obsoletes | RFC 4627 NERFINISHED ⓘ |
| organization | Internet Engineering Task Force NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo | JSON NERFINISHED ⓘ |
| series | Request for Comments NERFINISHED ⓘ |
| specifies |
JSON grammar
ⓘ
media type application/json ⓘ rules for JSON parsers and generators ⓘ |
| standardizes | text-based data interchange format ⓘ |
| status | Obsoleted ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| subject |
application protocols
ⓘ
data formats ⓘ |
| title | The JavaScript Object Notation (JSON) Data Interchange Format NERFINISHED ⓘ |
| updates | RFC 4627 NERFINISHED ⓘ |
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 7158 Description of subject: RFC 7158 is an IETF specification that updates and clarifies the JSON (JavaScript Object Notation) data interchange format previously defined in RFC 4627.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.