RFC 1310
E879416
RFC 1310 was an early document in the Internet standards process that outlined procedures and guidelines for developing and standardizing Internet protocols before being superseded by RFC 2026.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1310 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T10623785 — 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 1310 Context triple: [RFC 2026, obsoletes, RFC 1310]
-
A.
RFC 1031
RFC 1031 is an early Internet standards document that specified guidelines for the implementation and operation of certain TCP/IP networking protocols before being superseded by later updates.
-
B.
RFC 1910
RFC 1910 is an older Internet standards document related to network management that was later superseded by RFC 3410.
-
C.
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.
-
D.
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.
-
E.
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.
- 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 1310 Target entity description: RFC 1310 was an early document in the Internet standards process that outlined procedures and guidelines for developing and standardizing Internet protocols before being superseded by RFC 2026.
-
A.
RFC 1031
RFC 1031 is an early Internet standards document that specified guidelines for the implementation and operation of certain TCP/IP networking protocols before being superseded by later updates.
-
B.
RFC 1910
RFC 1910 is an older Internet standards document related to network management that was later superseded by RFC 3410.
-
C.
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.
-
D.
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.
-
E.
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.
- F. None of above. chosen
Statements (30)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
Request for Comments ⓘ |
| appliesTo | Internet protocols ⓘ |
| category | Standards Process ⓘ |
| defines |
Internet standards process
ⓘ
guidelines for developing Internet protocols ⓘ maturity levels for Internet standards ⓘ procedures for Internet standardization ⓘ requirements for Internet standard track ⓘ |
| describes |
Internet standards track
ⓘ
requirements for Draft Standard ⓘ requirements for Internet Standard ⓘ requirements for Proposed Standard ⓘ |
| governs | development of Internet protocol standards prior to RFC 2026 ⓘ |
| hasSuccessor | RFC 2026 NERFINISHED ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 2026 NERFINISHED ⓘ |
| partOfSeries | RFC series NERFINISHED ⓘ |
| publishedBy |
Internet Activities Board
NERFINISHED
ⓘ
Internet Engineering Task Force ⓘ |
| relation | early document in the Internet standards process ⓘ |
| replacedByProcessDefinedIn | RFC 2026 NERFINISHED ⓘ |
| seriesNumber | 1310 ⓘ |
| standardizes |
criteria for elevation to Internet Standard
ⓘ
procedures for advancing specifications on the standards track ⓘ roles of IAB and IETF in standards process ⓘ |
| status | Best Current Practice ⓘ |
| title | The Internet Standards Process NERFINISHED ⓘ |
| topic |
Internet protocol standardization
ⓘ
Internet standards ⓘ |
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 1310 Description of subject: RFC 1310 was an early document in the Internet standards process that outlined procedures and guidelines for developing and standardizing Internet protocols before being superseded by RFC 2026.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.