Triple
T36657034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PEP 614 |
E905021
|
entity |
| Predicate | implementedInVersion |
P181744
|
FINISHED |
| Object | Python 3.9 |
—
|
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: Python 3.9 | Statement: [PEP 614, implementedInVersion, Python 3.9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementedInVersion Context triple: [PEP 614, implementedInVersion, Python 3.9]
-
A.
introducedVersionOf
chosen
Indicates that one entity is the version in which another entity was first introduced or made available.
-
B.
historicallyImplementedIn
Indicates that an action, practice, or system was carried out or put into effect in a particular place or context during a past historical period.
-
C.
resultImplementedOn
Indicates that a particular result, outcome, or decision has been put into effect or applied on a specific entity, system, or context.
-
D.
alsoAvailableInVersion
Indicates that the same item, feature, or content is offered in another specified version or edition.
-
E.
implementedOn
Indicates that something (such as a feature, standard, or specification) is realized, executed, or put into effect within or on a particular platform, system, or environment.
- 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:11 p.m.