PEP 483
E911254
PEP 483 is a Python Enhancement Proposal that lays out the theoretical foundations and design principles for Python’s type hinting and generic types system.
All labels observed (1)
| Label | Occurrences |
|---|---|
| PEP 483 canonical | 3 |
How this entity was disambiguated
This entity first appeared as the object of triple T11215871 — 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 483 Context triple: [Python generic types, formalizedIn, PEP 483]
-
A.
PEP 624
PEP 624 is a Python Enhancement Proposal that specifies the removal of the Py_UNICODE encoder APIs from the CPython C API to streamline and modernize Unicode handling in Python.
-
B.
PEP 618
PEP 618 is a Python Enhancement Proposal that introduced the `strict` parameter to the built-in `zip` function, enabling stricter handling of iterables with mismatched lengths.
-
C.
PEP 604
PEP 604 is a Python Enhancement Proposal that introduced the modern, concise syntax for expressing type unions (using the `|` operator) in Python’s type hints.
-
D.
PEP 613
PEP 613 is a Python Enhancement Proposal that introduces the `TypeAlias` annotation to clearly declare and distinguish type aliases in Python’s type hinting system.
-
E.
PEP 634
PEP 634 is the Python Enhancement Proposal that formally specifies the semantics of structural pattern matching introduced in Python 3.10.
- 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 483 Target entity description: PEP 483 is a Python Enhancement Proposal that lays out the theoretical foundations and design principles for Python’s type hinting and generic types system.
-
A.
PEP 624
PEP 624 is a Python Enhancement Proposal that specifies the removal of the Py_UNICODE encoder APIs from the CPython C API to streamline and modernize Unicode handling in Python.
-
B.
PEP 618
PEP 618 is a Python Enhancement Proposal that introduced the `strict` parameter to the built-in `zip` function, enabling stricter handling of iterables with mismatched lengths.
-
C.
PEP 604
PEP 604 is a Python Enhancement Proposal that introduced the modern, concise syntax for expressing type unions (using the `|` operator) in Python’s type hints.
-
D.
PEP 613
PEP 613 is a Python Enhancement Proposal that introduces the `TypeAlias` annotation to clearly declare and distinguish type aliases in Python’s type hinting system.
-
E.
PEP 634
PEP 634 is the Python Enhancement Proposal that formally specifies the semantics of structural pattern matching introduced in Python 3.10.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf | Python Enhancement Proposal ⓘ |
| author | Ivan Levkivskyi ⓘ |
| category |
Typing PEP
ⓘ
linked to:
typing
|
| clarifies |
difference between runtime isinstance checks and static type checking
ⓘ
treatment of None and Optional ⓘ treatment of containers with type parameters ⓘ use of Any in type hints ⓘ use of Union types ⓘ |
| createdFor | Python type hinting ecosystem ⓘ |
| defines |
design principles for Python’s type system
ⓘ
theoretical foundations of Python type hints ⓘ |
| explains |
how type hints interact with duck typing
ⓘ
how type hints should be interpreted by type checkers ⓘ use of protocols for structural subtyping ⓘ |
| hostLanguage | English ⓘ |
| influences |
type checkers for Python
ⓘ
typing module design ⓘ |
| language | Python ⓘ |
| maintainer | Python core developers ⓘ |
| number | 483 ⓘ |
| precedes | PEP 484 ⓘ |
| relatedTo |
PEP 526
ⓘ
PEP 544 ⓘ PEP 560 ⓘ |
| relatesTo | PEP 484 ⓘ |
| repository | Python PEPs repository ⓘ |
| scope |
container and collection typing
ⓘ
contravariance ⓘ covariance ⓘ generic classes ⓘ invariance ⓘ nominal vs structural typing in Python ⓘ relationship between runtime and static types ⓘ semantics of type hints ⓘ type parameterization ⓘ |
| status | Accepted ⓘ |
| title | The Theory of Type Hints ⓘ |
| topic |
generic types
ⓘ
protocols ⓘ static typing ⓘ subtyping ⓘ type hints ⓘ typing semantics ⓘ variance ⓘ |
| type |
Informational PEP
ⓘ
linked to:
PEPs
|
| url | https://peps.python.org/pep-0483/ ⓘ |
| usedBy |
Python library authors
ⓘ
type checker authors ⓘ typing module designers ⓘ |
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 483 Description of subject: PEP 483 is a Python Enhancement Proposal that lays out the theoretical foundations and design principles for Python’s type hinting and generic types system.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.
subject linked to:
typing