RFC 1666
E261251
RFC 1666 is an early Internet standards document that was later superseded by RFC 1901 as the protocol or specification it defined evolved.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1666 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1777496 — 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 1666 Context triple: [RFC 1901, obsoletes, RFC 1666]
-
A.
RFC 1665
RFC 1665 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
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 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.
-
D.
RFC 1664
RFC 1664 is an early Internet standards document that defined a now-obsolete mechanism related to email or messaging services, later superseded by RFC 1901.
-
E.
RFC 1663
RFC 1663 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for serial line communication.
- 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 1666 Target entity description: RFC 1666 is an early Internet standards document that was later superseded by RFC 1901 as the protocol or specification it defined evolved.
-
A.
RFC 1665
RFC 1665 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
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 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.
-
D.
RFC 1664
RFC 1664 is an early Internet standards document that defined a now-obsolete mechanism related to email or messaging services, later superseded by RFC 1901.
-
E.
RFC 1663
RFC 1663 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for serial line communication.
- F. None of above. chosen
Statements (20)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
Request for Comments ⓘ |
| area | Network Management ⓘ |
| category | Experimental ⓘ |
| defines |
MIB objects for managing relational database systems via SNMP
ⓘ
mechanisms for RDBMS support within SNMP-based management ⓘ |
| format | Text ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 1901 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relation | early specification in the evolution of SNMP-based RDBMS management ⓘ |
| RFCNumber | 1666 ⓘ |
| series |
STD / RFC Series
ⓘ
linked to:
RFCs
|
| standardsTrack | no ⓘ |
| status | Obsoleted ⓘ |
| supersededBy | RFC 1901 ⓘ |
| title | Relational Database Management System (RDBMS) Support for SNMP ⓘ |
| 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 1666 Description of subject: RFC 1666 is an early Internet standards document that was later superseded by RFC 1901 as the protocol or specification it defined evolved.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.