RFC 3727
E826114
RFC 3727 is an Internet Engineering Task Force (IETF) document that defined earlier specifications for LDAP-related schema or matching rules, later superseded by RFC 4517.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 3727 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T9865292 — 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 3727 Context triple: [RFC 4517, obsoletes, RFC 3727]
-
A.
RFC 3207
RFC 3207 is the Internet standard that specifies the STARTTLS extension for upgrading plain text email connections to use TLS encryption in SMTP.
-
B.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
-
C.
RFC 2467
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
-
D.
RFC 3947
RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
-
E.
RFC 2487
RFC 2487 is an Internet standards document that originally defined the STARTTLS extension for securing SMTP connections with TLS, later superseded by RFC 3207.
- 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 3727 Target entity description: RFC 3727 is an Internet Engineering Task Force (IETF) document that defined earlier specifications for LDAP-related schema or matching rules, later superseded by RFC 4517.
-
A.
RFC 3207
RFC 3207 is the Internet standard that specifies the STARTTLS extension for upgrading plain text email connections to use TLS encryption in SMTP.
-
B.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
-
C.
RFC 2467
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
-
D.
RFC 3947
RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
-
E.
RFC 2487
RFC 2487 is an Internet standards document that originally defined the STARTTLS extension for securing SMTP connections with TLS, later superseded by RFC 3207.
- F. None of above. chosen
Statements (30)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard-track document
ⓘ
Request for Comments ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines |
ASN.1 modules for LDAP
ⓘ
LDAP matching rule representations in ASN.1 NERFINISHED ⓘ LDAP schema elements in ASN.1 ⓘ |
| definesFor |
LDAP-related matching rules
ⓘ
LDAP-related schema ⓘ |
| format | text ⓘ |
| hasNumber | 3727 ⓘ |
| isSupersededBy | RFC 4517 NERFINISHED ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 4517 NERFINISHED ⓘ |
| partOfSeries | RFC series NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedToProtocol |
LDAP
NERFINISHED
ⓘ
Lightweight Directory Access Protocol NERFINISHED ⓘ |
| standardizedBy | IETF Applications Area NERFINISHED ⓘ |
| standardsBody | Internet Engineering Task Force NERFINISHED ⓘ |
| status | Obsoleted ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| subject |
Directory protocols
ⓘ
Directory schemas ⓘ Directory services ⓘ Internet standards ⓘ |
| title | ASN.1 Module Definitions for the Lightweight Directory Access Protocol (LDAP) NERFINISHED ⓘ |
| updatesSpecificationFamily | LDAPv3 ⓘ |
| usesNotation | ASN.1 NERFINISHED ⓘ |
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 3727 Description of subject: RFC 3727 is an Internet Engineering Task Force (IETF) document that defined earlier specifications for LDAP-related schema or matching rules, later superseded by RFC 4517.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.