Triple
T34594936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CPython Git repository |
E888282
|
entity |
| Predicate | relatedDocumentation |
P19741
|
FINISHED |
| Object | https://devguide.python.org/ |
—
|
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://devguide.python.org/ | Statement: [CPython Git repository, relatedDocumentation, https://devguide.python.org/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedDocumentation Context triple: [CPython Git repository, relatedDocumentation, https://devguide.python.org/]
-
A.
relatedPass
Indicates that one pass is associated with or connected to another pass in some relevant way.
-
B.
linkedDocument
chosen
Indicates that one document is associated with or references another document in a meaningful way.
-
C.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
-
D.
relatedService
Indicates that one service is connected or associated with another service in a relevant or dependent way.
-
E.
relatedLibrary
Indicates that one library has a meaningful connection or association with another library, such as dependency, compatibility, or functional similarity.
- 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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:03 a.m.