RFC 0983
E330408
RFC 0983 is an early Internet standards document that specified protocols or requirements later superseded and refined by RFC 1122.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 0983 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T3081736 — 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 0983 Context triple: [RFC 1122, obsoletes, RFC 0983]
-
A.
RFC 0960
RFC 0960 is an early Internet standards document that specified aspects of TCP/IP networking behavior later superseded by RFC 1122.
-
B.
RFC 973
RFC 973 is an early Internet standards document that refines and extends the domain name system concepts introduced in RFC 882.
-
C.
RFC 783
RFC 783 is the original specification that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
-
D.
RFC 974
RFC 974 is an early Internet standard that defined the original mechanisms for mail routing and the use of MX records in the Domain Name System (DNS).
-
E.
RFC 950
RFC 950 is an Internet standard that defines the procedures and format for subnetting IP networks, extending the original IPv4 addressing scheme.
- 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 0983 Target entity description: RFC 0983 is an early Internet standards document that specified protocols or requirements later superseded and refined by RFC 1122.
-
A.
RFC 0960
RFC 0960 is an early Internet standards document that specified aspects of TCP/IP networking behavior later superseded by RFC 1122.
-
B.
RFC 973
RFC 973 is an early Internet standards document that refines and extends the domain name system concepts introduced in RFC 882.
-
C.
RFC 783
RFC 783 is the original specification that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
-
D.
RFC 974
RFC 974 is an early Internet standard that defined the original mechanisms for mail routing and the use of MX records in the Domain Name System (DNS).
-
E.
RFC 950
RFC 950 is an Internet standard that defines the procedures and format for subnetting IP networks, extending the original IPv4 addressing scheme.
- F. None of above. chosen
Statements (20)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
Request for Comments ⓘ |
| category | Standards Track ⓘ |
| countryOfOrigin |
United States
ⓘ
linked to:
United States of America
|
| defines | early Internet protocol requirements ⓘ |
| distribution | Public ⓘ |
| hasRFCNumber | 983 ⓘ |
| hasSuccessor | RFC 1122 ⓘ |
| language | English ⓘ |
| maintainedBy | RFC Editor ⓘ |
| medium | Text document ⓘ |
| obsoletedBy | RFC 1122 ⓘ |
| partOf | early Internet standards ⓘ |
| publishedBy |
Internet Activities Board
ⓘ
Internet Engineering Task Force ⓘ |
| publishedInSeries | RFC series ⓘ |
| relatedTo |
Internet Protocol Suite
ⓘ
linked to:
TCP/IP
TCP/IP ⓘ |
| status | Obsoleted ⓘ |
| subjectMatter | Internet host requirements ⓘ |
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 0983 Description of subject: RFC 0983 is an early Internet standards document that specified protocols or requirements later superseded and refined by RFC 1122.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.