PEP 613 TypeAlias annotation
E884132
PEP 613 TypeAlias annotation is a Python typing feature that introduces a dedicated `TypeAlias` marker to clearly distinguish type alias declarations from regular variable assignments.
All labels observed (2)
| Label | Occurrences |
|---|---|
| Explicit Type Aliases | 2 |
| PEP 613 TypeAlias annotation canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T10763915 — 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 613 TypeAlias annotation Context triple: [Python 3.10, hasTypingFeature, PEP 613 TypeAlias annotation]
-
A.
PEP 484
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.
-
B.
PEP 585
PEP 585 is a Python Enhancement Proposal that introduced built-in generic types (like list[int] and dict[str, int]) as a modern replacement for many typing module aliases.
-
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 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.
-
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 613 TypeAlias annotation Target entity description: PEP 613 TypeAlias annotation is a Python typing feature that introduces a dedicated `TypeAlias` marker to clearly distinguish type alias declarations from regular variable assignments.
-
A.
PEP 484
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.
-
B.
PEP 585
PEP 585 is a Python Enhancement Proposal that introduced built-in generic types (like list[int] and dict[str, int]) as a modern replacement for many typing module aliases.
-
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 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.
-
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 (31)
| Predicate | Object |
|---|---|
| instanceOf |
PEP
ⓘ
Python typing feature ⓘ |
| affects | static analysis tools ⓘ |
| appliesTo | Python type hints ⓘ |
| backwardsCompatibleWith | existing type hints ⓘ |
| category | typing and type system ⓘ |
| clarifies |
when a name is a normal variable
ⓘ
when a name is a type alias ⓘ |
| definesConcept | explicit type alias ⓘ |
| definesName | TypeAlias ⓘ |
| encourages | explicit type alias declarations in codebases ⓘ |
| example | Vector = list[float] ⓘ |
| exampleWithMarker | Vector: TypeAlias = list[float] ⓘ |
| hasTitle |
Explicit Type Aliases
ⓘ
linked to:
PEP 613 TypeAlias annotation
|
| introducedMarker | TypeAlias ⓘ |
| language | Python ⓘ |
| motivates | clear distinction between type aliases and variables ⓘ |
| partOf | typing module ⓘ |
| primaryGoal | make type alias declarations explicit ⓘ |
| relatedTo |
PEP 484
ⓘ
PEP 585 ⓘ PEP 604 ⓘ |
| relevantFor |
PyCharm type checker
ⓘ
mypy ⓘ pyright ⓘ
linked to:
Pyright
static type checkers ⓘ |
| solvesProblem | ambiguity between type alias declarations and regular assignments ⓘ |
| status | Accepted ⓘ |
| TypeAliasIs | special typing marker ⓘ |
| TypeAliasLivesIn | typing module ⓘ |
| usesSyntax | TypeAlias = ... ⓘ |
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 613 TypeAlias annotation Description of subject: PEP 613 TypeAlias annotation is a Python typing feature that introduces a dedicated `TypeAlias` marker to clearly distinguish type alias declarations from regular variable assignments.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: PEP 613 TypeAlias annotation