RFC 1010
E325858
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.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1010 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T3081739 — 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 1010 Context triple: [RFC 1122, obsoletes, RFC 1010]
-
A.
RFC 1910
RFC 1910 is an older Internet standards document related to network management that was later superseded by RFC 3410.
-
B.
RFC 1660
RFC 1660 is an early Internet standards document that specified an initial version of the Simple Network Management Protocol (SNMP) over OSI transport services before being superseded by later RFCs.
-
C.
RFC 1670
RFC 1670 is an early Internet standards document related to network protocols that was later superseded by RFC 1901.
-
D.
RFC 1661
RFC 1661 is the original specification of the Point-to-Point Protocol (PPP), defining a standard method for transporting multi-protocol datagrams over point-to-point links.
-
E.
RFC 1730
RFC 1730 is an early specification of the Internet Message Access Protocol (IMAP) that was later superseded by RFC 3501.
- 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 1010 Target entity description: 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.
-
A.
RFC 1910
RFC 1910 is an older Internet standards document related to network management that was later superseded by RFC 3410.
-
B.
RFC 1660
RFC 1660 is an early Internet standards document that specified an initial version of the Simple Network Management Protocol (SNMP) over OSI transport services before being superseded by later RFCs.
-
C.
RFC 1670
RFC 1670 is an early Internet standards document related to network protocols that was later superseded by RFC 1901.
-
D.
RFC 1661
RFC 1661 is the original specification of the Point-to-Point Protocol (PPP), defining a standard method for transporting multi-protocol datagrams over point-to-point links.
-
E.
RFC 1730
RFC 1730 is an early specification of the Internet Message Access Protocol (IMAP) that was later superseded by RFC 3501.
- F. None of above. chosen
Statements (42)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
Request for Comments ⓘ |
| area |
the internet
ⓘ
surface form:
Internet
|
| category |
Internet Assigned Numbers Authority
ⓘ
surface form:
Assigned Numbers
|
| defines |
official list of Internet protocol numbers
ⓘ
official list of link numbers ⓘ official list of machine names ⓘ official list of network numbers ⓘ official list of port numbers ⓘ official list of socket numbers ⓘ |
| documentType | Standards-related information ⓘ |
| followedBy | later assigned numbers RFCs ⓘ |
| language | English ⓘ |
| maintainedBy | Internet Assigned Numbers Authority ⓘ |
| obsoletedBy |
RFC 1060
ⓘ
RFC 1340 ⓘ RFC 1700 ⓘ RFC 3232 ⓘ |
| partOf |
IETF Internet standards process
ⓘ
surface form:
Internet standards process
|
| publishedBy |
Internet Engineering Task Force
ⓘ
Network Information Center ⓘ |
| publisher |
Network Information Center
ⓘ
surface form:
SRI International Network Information Center
|
| relatedTo |
Internet protocol parameter assignments
ⓘ
surface form:
IANA protocol parameter registry
TCP/IP ⓘ
surface form:
Internet protocol suite
TCP/IP ⓘ |
| replaced | earlier assigned numbers RFCs ⓘ |
| RFCNumber | 1010 ⓘ |
| scope | Internet-wide ⓘ |
| series |
RFCs
ⓘ
surface form:
RFC
|
| standardizationStage | Informational reference for assigned numbers at time of publication ⓘ |
| status | Historic ⓘ |
| subject |
Assigned link numbers
ⓘ
Assigned machine names ⓘ Assigned network numbers ⓘ Assigned port numbers ⓘ Assigned protocol numbers ⓘ Assigned protocol types ⓘ Assigned socket numbers ⓘ Internet protocol parameter assignments ⓘ |
| title |
Internet Assigned Numbers Authority
ⓘ
surface form:
Assigned Numbers
|
| useCase |
reference for network administrators
ⓘ
reference for protocol implementers ⓘ |
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 1010 Description of subject: 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.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.