Triple
T10826199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PEP 8016 |
E255502
|
entity |
| Predicate | pepIndexUrl |
P6055
|
FINISHED |
| Object | https://peps.python.org/pep-8016/ |
—
|
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: https://peps.python.org/pep-8016/ | Statement: [PEP 8016, pepIndexUrl, https://peps.python.org/pep-8016/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pepIndexUrl Context triple: [PEP 8016, pepIndexUrl, https://peps.python.org/pep-8016/]
-
A.
accessURL
chosen
Indicates the web address or endpoint through which a resource can be accessed or retrieved.
-
B.
registryURL
Indicates the web address where an entity’s official registration information is stored or can be accessed.
-
C.
endpointOnPeninsula
Indicates that one endpoint of an object, path, or feature lies on or within the bounds of a peninsula.
-
D.
PSE
Indicates a relationship where one entity is engaged in or associated with a public service or public sector employment role relative to another entity or context.
-
E.
peg
Indicates that one entity is fastened, secured, or fixed in place to another entity using a peg-like object or mechanism.
- 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.