Triple
T17557065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PEP 440 |
E427615
|
entity |
| Predicate | replaces |
P101
|
FINISHED |
| Object |
PEP 386
PEP 386 is a Python Enhancement Proposal that originally specified a version identification scheme for Python software distributions before being superseded by PEP 440.
|
E1275189
|
NE FINISHED |
How this triple was built (4 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
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).
Input
Phrase: PEP 386 | Statement: [PEP 440, replaces, PEP 386]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PEP 386 Context triple: [PEP 440, replaces, PEP 386]
-
A.
PEP 483
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.
-
B.
PEP 3107
PEP 3107 is the Python Enhancement Proposal that introduced function annotations, providing a standardized syntax for attaching metadata such as type information to function parameters and return values.
-
C.
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.
-
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 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.
NEDg
Description generation
gpt-5.1
Instruction
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]"
Input
Entity: PEP 386 Triple: [PEP 440, replaces, PEP 386]
Generated description
PEP 386 is a Python Enhancement Proposal that originally specified a version identification scheme for Python software distributions before being superseded by PEP 440.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: PEP 386 Target entity description: PEP 386 is a Python Enhancement Proposal that originally specified a version identification scheme for Python software distributions before being superseded by PEP 440.
-
A.
PEP 483
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.
-
B.
PEP 3107
PEP 3107 is the Python Enhancement Proposal that introduced function annotations, providing a standardized syntax for attaching metadata such as type information to function parameters and return values.
-
C.
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.
-
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 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
Provenance (5 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4562357b48190bde6f49df0c983c2 |
completed | April 19, 2026, 4:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01d2948ae0819083b90516b11d2485 |
completed | May 11, 2026, 12:59 p.m. |
| NEDg | Description generation | batch_6a01d43430d481909b07d8ecc09a185f |
completed | May 11, 2026, 1:05 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a01d4c609fc819089147744317d4be3 |
completed | May 11, 2026, 1:08 p.m. |
Created at: April 10, 2026, 5:50 a.m.