Triple
T37293604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PEP 552 |
E925734
|
entity |
| Predicate | targetsImplementation |
P150488
|
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 552, targetsImplementation, CPython]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetsImplementation Context triple: [PEP 552, targetsImplementation, CPython]
-
A.
implementationTarget
chosen
Indicates that one entity serves as the concrete implementation or realization of another entity’s specification, interface, or design.
-
B.
targetsUseCase
Indicates that one entity is aimed at or designed to address a particular use case associated with another entity.
-
C.
targetsProvidedBy
Indicates that one entity supplies or makes available specific targets for another entity to use or act upon.
-
D.
targetsProvision
Indicates that one entity is the intended recipient or beneficiary of a provision, service, or resource supplied by another entity.
-
E.
targetsAPI
Indicates that one entity is designed to interact with, call, or be compatible with a specific API.
- 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_69f76eb0f86c819098dee07393e69ec3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff2636e2bc8190bba91eff91431c6e |
completed | May 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69ff25c65be48190868480d94e1c4e89 |
completed | May 9, 2026, 12:17 p.m. |
Created at: May 3, 2026, 4:16 p.m.