RFC 1667
E263365
RFC 1667 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1667 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1777497 — 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 1667 Context triple: [RFC 1901, obsoletes, RFC 1667]
-
A.
RFC 1657
RFC 1657 is an early Internet standards document that defined SNMPv2 Management Information Base (MIB) extensions for managing BGP-4 routing protocol implementations.
-
B.
RFC 1666
RFC 1666 is an early Internet standards document that was later superseded by RFC 1901 as the protocol or specification it defined evolved.
-
C.
RFC 1665
RFC 1665 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
D.
RFC 1652
RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
-
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 1667 Target entity description: RFC 1667 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
A.
RFC 1657
RFC 1657 is an early Internet standards document that defined SNMPv2 Management Information Base (MIB) extensions for managing BGP-4 routing protocol implementations.
-
B.
RFC 1666
RFC 1666 is an early Internet standards document that was later superseded by RFC 1901 as the protocol or specification it defined evolved.
-
C.
RFC 1665
RFC 1665 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
D.
RFC 1652
RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
-
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 (15)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
Request for Comments ⓘ |
| documentType | standards-track specification ⓘ |
| language | English ⓘ |
| medium | text ⓘ |
| obsoletedBy | RFC 1901 ⓘ |
| partOfSeries |
RFC series
ⓘ
linked to:
RFCs
|
| protocolSpecification | an early version of an Internet protocol later revised in RFC 1901 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| RFCNumber | 1667 ⓘ |
| status | obsoleted ⓘ |
| subject |
Internet protocol design
ⓘ
Internet standards ⓘ |
| supersededBy | RFC 1901 ⓘ |
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 1667 Description of subject: RFC 1667 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.