Triple
T10826168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PEP 8016 |
E255502
|
entity |
| Predicate | acceptedDate |
P14303
|
FINISHED |
| Object | 2018-12-17 |
—
|
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: 2018-12-17 | Statement: [PEP 8016, acceptedDate, 2018-12-17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceptedDate Context triple: [PEP 8016, acceptedDate, 2018-12-17]
-
A.
acceptedAt
Indicates the time or event at which something (such as a request, submission, or offer) is formally accepted.
-
B.
approvalDate
chosen
Indicates the date on which an action, request, or item was formally approved.
-
C.
agreedAt
Indicates the time or point at which an agreement or consensus between parties was reached.
-
D.
acceptedIn
Indicates that something has been formally received, approved, or admitted into a particular context, group, or system.
-
E.
acknowledgmentDate
Indicates the date on which an acknowledgment of something (such as receipt, notice, or information) is formally recorded or recognized.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d734d1c24881909f56d56207cccbef |
completed | April 9, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69d70d1bf3648190b36fa96ea018e0dc |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.