Triple
T36396971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PEP 590 |
E896510
|
entity |
| Predicate | acceptedInYear |
P62976
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [PEP 590, acceptedInYear, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceptedInYear Context triple: [PEP 590, acceptedInYear, 2019]
-
A.
acceptedIn
Indicates that something has been formally received, approved, or admitted into a particular context, group, or system.
-
B.
endorsedInYear
Indicates that one entity formally expressed support or approval for another entity during a specified calendar year.
-
C.
yearApproved
chosen
Indicates the specific year in which something (such as a proposal, product, or decision) was formally approved.
-
D.
claimedYear
Indicates the year that is asserted or reported as being associated with an event, status, or fact, regardless of whether it is verified.
-
E.
authorizationYear
Indicates the year in which an official approval, permission, or authorization for something was granted.
- 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.