Triple
T36396939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PEP 590 |
E896510
|
entity |
| Predicate | targetImplementation |
P43638
|
FINISHED |
| Object | CPython |
—
|
NE NERFINISHED |
How this triple was built (2 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: CPython | Statement: [PEP 590, targetImplementation, CPython]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetImplementation Context triple: [PEP 590, targetImplementation, CPython]
-
A.
implementationTarget
Indicates that one entity serves as the concrete implementation or realization of another entity’s specification, interface, or design.
-
B.
mainImplementer
Indicates that an entity is the primary party responsible for carrying out, developing, or executing a specified action, project, or implementation.
-
C.
isImplementationOf
chosen
Indicates that one entity realizes, fulfills, or concretely carries out the specification, interface, or abstract definition provided by another entity.
-
D.
aimedToImplement
Indicates that an entity had the intention or plan to carry out, realize, or put another entity (such as a policy, idea, or system) into effect.
-
E.
currentlyImplementedBy
Indicates that a given specification, design, or feature is presently realized or supported by a particular implementation or system.
- F. None of above.
Provenance (3 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff0b6bc4a88190bf1d38c6ea26bcdc |
completed | May 9, 2026, 10:24 a.m. |
| PD | Predicate disambiguation | batch_69ff082a22f4819095ded971dbd8ea7b |
completed | May 9, 2026, 10:10 a.m. |
Created at: May 3, 2026, 4:10 p.m.