Triple
T36657030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PEP 614 |
E905021
|
entity |
| Predicate | proposesChange |
P21476
|
FINISHED |
| Object | relax grammar restrictions on decorator syntax |
—
|
LITERAL FINISHED |
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: relax grammar restrictions on decorator syntax | Statement: [PEP 614, proposesChange, relax grammar restrictions on decorator syntax]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposesChange Context triple: [PEP 614, proposesChange, relax grammar restrictions on decorator syntax]
-
A.
proposalType
Indicates the specific category or kind of proposal associated with an entity or event.
-
B.
featureChange
Indicates a modification in the properties, characteristics, or attributes of an entity between two states or points in time.
-
C.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
-
D.
proposedAmendment
chosen
Indicates that one entity has formally suggested a change or addition (an amendment) to another entity, such as a document, law, or agreement.
-
E.
proposalNumber
Indicates that an entity is associated with a specific proposal identified by a unique number.
- 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_69f7c77907808190904959e4326fed7d |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.