RFC 1013
E330409
RFC 1013 is an early Internet standards document that specified aspects of TCP/IP protocol behavior before being superseded by later, more comprehensive specifications.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1013 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T3081741 — 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 1013 Context triple: [RFC 1122, obsoletes, RFC 1013]
-
A.
RFC 1813
RFC 1813 is the Internet Engineering Task Force (IETF) specification that defines version 3 of the Network File System (NFS) protocol.
-
B.
RFC 1663
RFC 1663 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for serial line communication.
-
C.
RFC 1012
RFC 1012 is an early Internet standards document that specified requirements and guidelines for host communication protocols before being superseded by later updates.
-
D.
RFC 1010
RFC 1010 was an early Internet standards document that provided an official list of assigned protocol numbers and related parameters before being superseded by later updates.
-
E.
RFC 1653
RFC 1653 is an older Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
- 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 1013 Target entity description: RFC 1013 is an early Internet standards document that specified aspects of TCP/IP protocol behavior before being superseded by later, more comprehensive specifications.
-
A.
RFC 1813
RFC 1813 is the Internet Engineering Task Force (IETF) specification that defines version 3 of the Network File System (NFS) protocol.
-
B.
RFC 1663
RFC 1663 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for serial line communication.
-
C.
RFC 1012
RFC 1012 is an early Internet standards document that specified requirements and guidelines for host communication protocols before being superseded by later updates.
-
D.
RFC 1010
RFC 1010 was an early Internet standards document that provided an official list of assigned protocol numbers and related parameters before being superseded by later updates.
-
E.
RFC 1653
RFC 1653 is an older Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
- F. None of above. chosen
Statements (30)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard-related document
ⓘ
Request for Comments document ⓘ |
| accessMethod | publicly available on the Internet ⓘ |
| appliesTo |
Internet gateways
ⓘ
Internet hosts ⓘ |
| category |
Internet standards
ⓘ
networking ⓘ |
| concerns | Internet protocol behavior ⓘ |
| documentType | technical specification ⓘ |
| governs | interoperability of TCP/IP implementations ⓘ |
| hasIdentifierType | RFC number ⓘ |
| hasRFCNumber | 1013 ⓘ |
| hasScope | early Internet standards ⓘ |
| influencedBy | early TCP/IP design practices ⓘ |
| language | English ⓘ |
| maintainedInRepository | RFC Editor archive ⓘ |
| medium | text document ⓘ |
| partOfSeries |
RFCs
ⓘ
surface form:
RFC series
|
| publishedBy |
Internet Activities Board
ⓘ
Internet Engineering Task Force ⓘ |
| publishedInContextOf | TCP/IP protocol suite ⓘ |
| relatedToProtocolFamily |
IP
ⓘ
Transmission Control Protocol ⓘ
surface form:
TCP
|
| standardizes | aspects of TCP/IP behavior ⓘ |
| status | obsolete ⓘ |
| supersededBy | later TCP/IP specifications ⓘ |
| targetAudience |
network engineers
ⓘ
protocol implementers ⓘ system administrators ⓘ |
| usedAs | reference for early TCP/IP implementations ⓘ |
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 1013 Description of subject: RFC 1013 is an early Internet standards document that specified aspects of TCP/IP protocol behavior before being superseded by later, more comprehensive specifications.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.