RFC 1451
E198872
RFC 1451 is an early Internet standards document related to network management that was later superseded by RFC 1901.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1451 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T1777474 — 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 1451 Context triple: [RFC 1901, obsoletes, RFC 1451]
-
A.
RFC 1591
RFC 1591 is an Internet standards document that defines the structure, administration, and delegation policies for top-level domains in the Domain Name System (DNS).
-
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 1195
RFC 1195 is the IETF standard that extends the IS-IS routing protocol to support multiple network layer protocols, including IP.
-
D.
RFC 3415
RFC 3415 is an Internet standard that specifies the View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP), defining how access to management information is controlled.
-
E.
RFC 1905
RFC 1905 is an Internet standards document that specifies the protocol operations for the Simple Network Management Protocol version 2 (SNMPv2).
- 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 1451 Target entity description: RFC 1451 is an early Internet standards document related to network management that was later superseded by RFC 1901.
-
A.
RFC 1591
RFC 1591 is an Internet standards document that defines the structure, administration, and delegation policies for top-level domains in the Domain Name System (DNS).
-
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 1195
RFC 1195 is the IETF standard that extends the IS-IS routing protocol to support multiple network layer protocols, including IP.
-
D.
RFC 3415
RFC 3415 is an Internet standard that specifies the View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP), defining how access to management information is controlled.
-
E.
RFC 1905
RFC 1905 is an Internet standards document that specifies the protocol operations for the Simple Network Management Protocol version 2 (SNMPv2).
- F. None of above. chosen
Statements (25)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
Request for Comments ⓘ |
| area | Network management ⓘ |
| category | Standards Track ⓘ |
| defines |
MIB objects for network management
ⓘ
Manager-to-Manager MIB ⓘ objects for manager-to-manager communication ⓘ |
| documentType | Technical specification ⓘ |
| focusesOn | manager-to-manager communication in network management ⓘ |
| intendedUse | Internet network management ⓘ |
| language | English ⓘ |
| networkLayer | Application layer ⓘ |
| obsoletedBy | RFC 1901 ⓘ |
| partOf | SNMP management framework ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedRFC | RFC 1901 ⓘ |
| RFCNumber | 1451 ⓘ |
| series |
Request for Comments
ⓘ
linked to:
RFCs
|
| standardsTrackStatus | Proposed Standard ⓘ |
| standardType | Internet Standard-related specification ⓘ |
| status | Obsoleted ⓘ |
| title | Manager-to-Manager Management Information Base ⓘ |
| updatesProtocol |
SNMP
ⓘ
Simple Network Management Protocol ⓘ
linked to:
SNMP
|
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 1451 Description of subject: RFC 1451 is an early Internet standards document related to network management that was later superseded by RFC 1901.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.