RFC 950
E60448
RFC 950 is an Internet standard that defines the procedures and format for subnetting IP networks, extending the original IPv4 addressing scheme.
All labels observed (2)
How this entity was disambiguated
This entity first appeared as the object of triple T482566 — 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 950 Context triple: [RFC 791, relatedTo, RFC 950]
-
A.
RFC 792
RFC 792 is the Internet standard document that specifies the Internet Control Message Protocol (ICMP), which is used for network diagnostics and error reporting in IP networks.
-
B.
RFC 1350
RFC 1350 is the Internet standards document that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
-
C.
RFC 855
RFC 855 is an Internet standards document that specifies the Telnet protocol’s options and mechanisms for remote terminal communication over TCP/IP networks.
-
D.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
E.
RFC 882
RFC 882 was an early Internet standard that originally specified the Domain Name System (DNS) protocol before being superseded by later RFCs such as RFC 1035.
- 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 950 Target entity description: RFC 950 is an Internet standard that defines the procedures and format for subnetting IP networks, extending the original IPv4 addressing scheme.
-
A.
RFC 792
RFC 792 is the Internet standard document that specifies the Internet Control Message Protocol (ICMP), which is used for network diagnostics and error reporting in IP networks.
-
B.
RFC 1350
RFC 1350 is the Internet standards document that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
-
C.
RFC 855
RFC 855 is an Internet standards document that specifies the Telnet protocol’s options and mechanisms for remote terminal communication over TCP/IP networks.
-
D.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
E.
RFC 882
RFC 882 was an early Internet standard that originally specified the Domain Name System (DNS) protocol before being superseded by later RFCs such as RFC 1035.
- F. None of above. chosen
Statements (38)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| appliesTo |
IPv4
ⓘ
classful IP addressing ⓘ |
| area |
the internet
ⓘ
surface form:
Internet
|
| author |
J. Mogul
ⓘ
Jonathan B. Postel ⓘ
surface form:
J. Postel
|
| category | Standards Track (at time of publication) ⓘ |
| defines |
format for subnetted IP addresses
ⓘ
rules for dividing a classful IP network into subnets ⓘ subnetting procedure for IP networks ⓘ |
| definesTerm |
subnet
ⓘ
subnet mask ⓘ subnetted network ⓘ |
| goal |
allow more flexible allocation of IP address space within organizations
ⓘ
extend the original IPv4 addressing scheme to support subnetting ⓘ |
| influenced |
design of later subnetting and CIDR standards
ⓘ
early IP routing implementations ⓘ |
| language | English ⓘ |
| obsoletedBy |
RFC 1812
ⓘ
later CIDR-related RFCs ⓘ |
| publicationMonth | August ⓘ |
| publicationYear | 1985 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publishedInSeries |
RFCs
ⓘ
surface form:
Request for Comments
|
| relatedTo |
IPv4
ⓘ
RFC 791 ⓘ |
| rfcNumber | 950 ⓘ |
| specifies |
broadcast address conventions for subnets
ⓘ
routing considerations for subnetted networks ⓘ rules for assigning host numbers within subnets ⓘ rules for assigning subnet numbers ⓘ subnet mask concept ⓘ use of a subnet field within the host portion of an IP address ⓘ |
| status | Historic ⓘ |
| title | Internet Standard Subnetting Procedure ⓘ |
| updates | IPv4 addressing scheme ⓘ |
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 950 Description of subject: RFC 950 is an Internet standard that defines the procedures and format for subnetting IP networks, extending the original IPv4 addressing scheme.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.