Triple
T14341507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Partial Evaluation and Program Manipulation |
E355614
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | PEPM |
E71963
|
NE 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: PEPM | Statement: [Partial Evaluation and Program Manipulation, hasAbbreviation, PEPM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PEPM Context triple: [Partial Evaluation and Program Manipulation, hasAbbreviation, PEPM]
-
A.
PEPM
chosen
PEPM (Partial Evaluation and Program Manipulation) is an ACM SIGPLAN-sponsored symposium focused on research in program analysis, transformation, and generation techniques.
-
B.
PEP
PEP is the stock ticker symbol for PepsiCo, the multinational food, snack, and beverage corporation traded on the NASDAQ.
-
C.
PEPs
PEPs are formal design documents that propose and describe new features, processes, or changes for the Python programming language and its community.
-
D.
PEP 8016
PEP 8016 is a Python Enhancement Proposal that defined a governance model for the Python project following Guido van Rossum’s retirement as BDFL.
-
E.
PE5
PE5 is a postcode district in the PE (Peterborough) postcode area of eastern England, covering a small rural region near Peterborough.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8e87febc8190a63c668cbd0fd713 |
completed | April 14, 2026, 6:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd4c3f81e881909f742d0442e99dd6 |
completed | May 8, 2026, 2:36 a.m. |
Created at: April 10, 2026, 1:14 a.m.