Triple

Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).

Phrase: RFC 7868 | Statement: [EIGRP, RFC, RFC 7868]

Target entity: RFC 7868
Context triple: [EIGRP, RFC, RFC 7868]

• A. RFC 6668
  RFC 6668 is an Internet Engineering Task Force (IETF) standard that updates the Secure Shell (SSH) protocol to add support for modern elliptic curve cryptography methods.
• B. RFC 5838
  RFC 5838 is an IETF specification that updates and extends OSPFv3 to support multiple address families, including IPv4 and IPv6, within a single protocol instance.
• C. RFC 8728
  RFC 8728 is an Internet Engineering Task Force (IETF) document that specifies updates and procedures related to the RFC Editor’s role in the publication process of RFCs.
• D. RFC 6860
  RFC 6860 is an Internet Engineering Task Force (IETF) standards-track document that updates and clarifies the use of cryptographic authentication for OSPFv3, superseding earlier specifications.
• E. RFC 7684
  RFC 7684 is an Internet Engineering Task Force (IETF) standards document that updates and replaces the earlier OSPFv3 specification defined in RFC 5340.
• F. None of above. chosen
• G. Unsure - the case is ambiguous/there is not enough information to decide.

Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"

Entity: RFC 7868
Triple: [EIGRP, RFC, RFC 7868]

RFC 7868 is the IETF specification that documents and standardizes the Enhanced Interior Gateway Routing Protocol (EIGRP) as an informational routing protocol.

Target entity: RFC 7868
Target entity description: RFC 7868 is the IETF specification that documents and standardizes the Enhanced Interior Gateway Routing Protocol (EIGRP) as an informational routing protocol.

• A. RFC 6668
  RFC 6668 is an Internet Engineering Task Force (IETF) standard that updates the Secure Shell (SSH) protocol to add support for modern elliptic curve cryptography methods.
• B. RFC 5838
  RFC 5838 is an IETF specification that updates and extends OSPFv3 to support multiple address families, including IPv4 and IPv6, within a single protocol instance.
• C. RFC 8728
  RFC 8728 is an Internet Engineering Task Force (IETF) document that specifies updates and procedures related to the RFC Editor’s role in the publication process of RFCs.
• D. RFC 6860
  RFC 6860 is an Internet Engineering Task Force (IETF) standards-track document that updates and clarifies the use of cryptographic authentication for OSPFv3, superseding earlier specifications.
• E. RFC 7684
  RFC 7684 is an Internet Engineering Task Force (IETF) standards document that updates and replaces the earlier OSPFv3 specification defined in RFC 5340.
• F. None of above. chosen

Target predicate: RFC
Context triple: [EIGRP, RFC, RFC 7868]

• A. originalRfc
  Indicates that something is the initial or authoritative RFC (Request for Comments) document from which a specification, standard, or later revision originates.
• B. relatedRFC chosen
  Indicates that one resource or specification is connected or associated with another through a shared or relevant RFC (Request for Comments) document.
• C. RIC
  Indicates a relationship in which one entity is responsible for insuring or providing insurance coverage to another entity or asset.
• D. onStandardsTrack
  Indicates that the subject is part of an officially recognized, actively developed standards process or pathway toward becoming a formal standard.
• E. relationToIETF
  Indicates the nature of an entity’s connection or involvement with the Internet Engineering Task Force (IETF), such as affiliation, participation, or oversight.
• F. None of above.