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: PEP 660 | Statement: [installer (PyPA project), conformsTo, PEP 660]

Target entity: PEP 660
Context triple: [installer (PyPA project), conformsTo, PEP 660]

• A. PEP 685
  PEP 685 is a Python Enhancement Proposal that introduces a standard for handling and normalizing direct URL references in Python package metadata to improve interoperability across packaging tools.
• B. PEP 636
  PEP 636 is a Python Enhancement Proposal that serves as a tutorial-style guide to the structural pattern matching feature introduced in Python 3.10.
• C. PEP 695
  PEP 695 is a Python Enhancement Proposal that introduces a new, more concise syntax for type parameter declarations to improve the language’s support for generics and static typing.
• D. PEP 657
  PEP 657 is a Python enhancement proposal that improves error reporting by adding fine-grained location information (such as per-expression line and column data) to tracebacks.
• E. PEP 626
  PEP 626 is a Python Enhancement Proposal that precisely defines how Python should map executed bytecode instructions to source code lines, improving debugging, coverage measurement, and tooling accuracy.
• 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: PEP 660
Triple: [installer (PyPA project), conformsTo, PEP 660]

PEP 660 is a Python packaging standard that defines how editable installs should work for PEP 517 build backends, enabling consistent development workflows across tools.

Target entity: PEP 660
Target entity description: PEP 660 is a Python packaging standard that defines how editable installs should work for PEP 517 build backends, enabling consistent development workflows across tools.

• A. PEP 685
  PEP 685 is a Python Enhancement Proposal that introduces a standard for handling and normalizing direct URL references in Python package metadata to improve interoperability across packaging tools.
• B. PEP 636
  PEP 636 is a Python Enhancement Proposal that serves as a tutorial-style guide to the structural pattern matching feature introduced in Python 3.10.
• C. PEP 695
  PEP 695 is a Python Enhancement Proposal that introduces a new, more concise syntax for type parameter declarations to improve the language’s support for generics and static typing.
• D. PEP 657
  PEP 657 is a Python enhancement proposal that improves error reporting by adding fine-grained location information (such as per-expression line and column data) to tracebacks.
• E. PEP 626
  PEP 626 is a Python Enhancement Proposal that precisely defines how Python should map executed bytecode instructions to source code lines, improving debugging, coverage measurement, and tooling accuracy.
• F. None of above. chosen