PEP 13
E53026
PEP 13 is the Python Enhancement Proposal that defines the process and rules for selecting and operating the Python Steering Council, the core governance body of the Python project.
All labels observed (1)
| Label | Occurrences |
|---|---|
| PEP 13 canonical | 7 |
How this entity was disambiguated
This entity first appeared as the object of triple T400421 — 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: PEP 13 Context triple: [Python Enhancement Proposals, hasPart, PEP 13]
-
A.
PEP 1
PEP 1 is the foundational Python Enhancement Proposal that defines the purpose, structure, and workflow for all other PEPs in the Python community process.
-
B.
PEP 0
PEP 0 is the index document that lists and tracks the status of all Python Enhancement Proposals (PEPs) in the Python community.
-
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 622
PEP 622 is a Python Enhancement Proposal that introduced the design for structural pattern matching syntax later adopted in Python 3.10.
-
E.
PEP 572
PEP 572 is the Python proposal that introduced the “walrus operator” (:=) for assignment expressions, allowing assignment within larger expressions.
- 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: PEP 13 Target entity description: PEP 13 is the Python Enhancement Proposal that defines the process and rules for selecting and operating the Python Steering Council, the core governance body of the Python project.
-
A.
PEP 1
PEP 1 is the foundational Python Enhancement Proposal that defines the purpose, structure, and workflow for all other PEPs in the Python community process.
-
B.
PEP 0
PEP 0 is the index document that lists and tracks the status of all Python Enhancement Proposals (PEPs) in the Python community.
-
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 622
PEP 622 is a Python Enhancement Proposal that introduced the design for structural pattern matching syntax later adopted in Python 3.10.
-
E.
PEP 572
PEP 572 is the Python proposal that introduced the “walrus operator” (:=) for assignment expressions, allowing assignment within larger expressions.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf | Python Enhancement Proposal ⓘ |
| appliesTo |
Python reference implementation (CPython)
ⓘ
surface form:
CPython core development
|
| audience |
Python Steering Council
ⓘ
surface form:
Python Steering Council members
Python contributors ⓘ Python core developers ⓘ |
| canBeAmendedBy | another accepted PEP ⓘ |
| createdAfter | Python governance crisis of 2018 ⓘ |
| defines |
Python Steering Council governance model
ⓘ
process for selecting the Python Steering Council ⓘ rules for operating the Python Steering Council ⓘ |
| documentationFormat | reStructuredText ⓘ |
| establishes | Python Steering Council ⓘ |
| governs | core governance of the Python project ⓘ |
| governsBody | Python Steering Council ⓘ |
| governsProject |
Python
ⓘ
surface form:
Python programming language
|
| hasSection |
Amendments
ⓘ
Conflicts of interest ⓘ Council elections ⓘ Council membership ⓘ Council powers ⓘ Vacancies and recalls ⓘ Voter roll ⓘ |
| hostedOn | Python PEP repository ⓘ |
| influences | decision-making in the Python project ⓘ |
| language | English ⓘ |
| maintainerRole | Python Steering Council ⓘ |
| relatedTo |
Python Steering Council elections
ⓘ
Python Enhancement Proposals ⓘ
surface form:
Python core development process
PEP 13: Python Language Governance ⓘ
surface form:
Python governance
|
| replaces | BDFL-centric governance model ⓘ |
| scope | governance of the Python language and its reference implementation ⓘ |
| specifies |
conflict of interest rules for Steering Council members
ⓘ
decision-making authority of the Steering Council ⓘ election process for the Python Steering Council ⓘ how PEP decisions are overseen by the Steering Council ⓘ how the Steering Council can delegate authority ⓘ how ties in elections are resolved ⓘ how vacancies on the Steering Council are handled ⓘ interaction between Steering Council and core developers ⓘ nomination rules for Steering Council candidates ⓘ recall or removal mechanisms for Steering Council members ⓘ size of the Python Steering Council ⓘ term length of the Python Steering Council ⓘ voter eligibility for Steering Council elections ⓘ |
| status | Active ⓘ |
| title |
PEP 13: Python Language Governance
ⓘ
surface form:
Python Language Governance
|
| type | Process PEP ⓘ |
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: PEP 13 Description of subject: PEP 13 is the Python Enhancement Proposal that defines the process and rules for selecting and operating the Python Steering Council, the core governance body of the Python project.
Referenced by (7)
Full triples — surface form annotated when it differs from this entity's canonical label.