Triple
T34594905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CPython Git repository |
E888282
|
entity |
| Predicate | canonicalURL |
P6055
|
FINISHED |
| Object | https://github.com/python/cpython |
—
|
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://github.com/python/cpython | Statement: [CPython Git repository, canonicalURL, https://github.com/python/cpython]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canonicalURL Context triple: [CPython Git repository, canonicalURL, https://github.com/python/cpython]
-
A.
canonicalFor
Indicates that one entity serves as the authoritative or standard representation for another, often consolidating or standing in for its variants or duplicates.
-
B.
canonicalContext
Indicates the standard or primary contextual framework within which an entity, statement, or resource is to be interpreted.
-
C.
hadURL
Indicates that an entity was associated with or linked to a specific URL at some point in time.
-
D.
canonicalFocus
Indicates that one entity is the primary or most representative focus or point of attention in relation to another entity.
-
E.
accessURL
chosen
Indicates the web address or endpoint through which a resource can be accessed or retrieved.
- 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_69f72ad38a208190b4bdc828297f86ad |
completed | May 3, 2026, 11 a.m. |
| PD | Predicate disambiguation | batch_69f72a0243988190a43b8ea22457cd30 |
completed | May 3, 2026, 10:57 a.m. |
Created at: May 1, 2026, 2:03 a.m.