PEP 484
E265441
PEP 484 is the Python Enhancement Proposal that introduced a standard for type hints in Python, forming the basis of the language’s static typing ecosystem.
All labels observed (2)
| Label | Occurrences |
|---|---|
| PEP 484 canonical | 4 |
| Python static type system | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T2417400 — 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 484 Context triple: [PEP 695, relatedTo, PEP 484]
-
A.
PEP 634
PEP 634 is the Python Enhancement Proposal that formally specifies the semantics of structural pattern matching introduced in Python 3.10.
-
B.
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.
-
C.
PEP 622
PEP 622 is a Python Enhancement Proposal that introduced the design for structural pattern matching syntax later adopted in Python 3.10.
-
D.
PEP 572
PEP 572 is the Python proposal that introduced the “walrus operator” (:=) for assignment expressions, allowing assignment within larger expressions.
-
E.
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.
- 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 484 Target entity description: PEP 484 is the Python Enhancement Proposal that introduced a standard for type hints in Python, forming the basis of the language’s static typing ecosystem.
-
A.
PEP 634
PEP 634 is the Python Enhancement Proposal that formally specifies the semantics of structural pattern matching introduced in Python 3.10.
-
B.
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.
-
C.
PEP 622
PEP 622 is a Python Enhancement Proposal that introduced the design for structural pattern matching syntax later adopted in Python 3.10.
-
D.
PEP 572
PEP 572 is the Python proposal that introduced the “walrus operator” (:=) for assignment expressions, allowing assignment within larger expressions.
-
E.
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.
- F. None of above. chosen
Statements (57)
| Predicate | Object |
|---|---|
| instanceOf | Python Enhancement Proposal ⓘ |
| appliesToLanguage | Python ⓘ |
| createdBy |
Guido van Rossum
ⓘ
Jukka Lehtosalo ⓘ Michael Sullivan ⓘ other contributors ⓘ Łukasz Langa ⓘ |
| createdForVersion |
Python 3.x
ⓘ
surface form:
Python 3.5
|
| defines |
semantics for type hints
ⓘ
standard typing module interfaces ⓘ syntax for type hints ⓘ typing module ⓘ typing.Any ⓘ Python typing module ⓘ
surface form:
typing.Callable
typing.Dict ⓘ typing.FrozenSet ⓘ typing.Generic ⓘ typing.IO ⓘ typing.Iterable ⓘ typing.List ⓘ Python typing module ⓘ
surface form:
typing.Mapping
typing.NewType ⓘ typing.Optional ⓘ typing.Sequence ⓘ typing.Set ⓘ typing.Tuple ⓘ typing.TypeVar ⓘ typing.Union ⓘ Python typing module ⓘ
surface form:
typing.overload
|
| formsBasisOf | Python static typing ecosystem ⓘ |
| governs | standard library typing module behavior ⓘ |
| hostedAt | https://peps.python.org/pep-0484/ ⓘ |
| influenced |
PyCharm type checking
ⓘ
Pyright ⓘ static analysis tools for Python ⓘ third-party type checkers such as mypy ⓘ |
| introducedConcept | static typing in Python ⓘ |
| introducedFeature |
standard for type hints
ⓘ
type hints ⓘ |
| introducedInVersion |
Python 3.x
ⓘ
surface form:
Python 3.5
|
| motivation |
enable static type checking for Python
ⓘ
improve tooling and IDE support ⓘ provide a standard way to add type information to Python code ⓘ |
| relatedTo |
PEP 3107
ⓘ
PEP 483 ⓘ PEP 526 ⓘ PEP 544 ⓘ |
| specifies |
conventions for gradual typing
ⓘ
how to annotate class attributes ⓘ how to annotate functions ⓘ how to annotate variables ⓘ rules for type checkers ⓘ stub file format .pyi ⓘ |
| status | Final ⓘ |
| title |
Python typing module
ⓘ
surface form:
Type Hints
|
| yearAccepted | 2015 ⓘ |
| yearProposed | 2014 ⓘ |
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 484 Description of subject: PEP 484 is the Python Enhancement Proposal that introduced a standard for type hints in Python, forming the basis of the language’s static typing ecosystem.
Referenced by (5)
Full triples — surface form annotated when it differs from this entity's canonical label.
this entity surface form:
Python static type system