Triple
T34594904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CPython Git repository |
E888282
|
entity |
| Predicate | primaryHostingService |
P11934
|
FINISHED |
| Object | GitHub |
E5697
|
NE 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: GitHub | Statement: [CPython Git repository, primaryHostingService, GitHub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryHostingService Context triple: [CPython Git repository, primaryHostingService, GitHub]
-
A.
primaryService
chosen
Indicates that one entity serves as the main or principal service provided or used in relation to another entity.
-
B.
primaryHosts
Indicates that the subject serves as the main or principal host for the object, such as an organism, event, or service.
-
C.
primaryServicePattern
Indicates the main or most typical way in which a service is delivered, structured, or utilized within a given context.
-
D.
primaryHubFor
Indicates that one entity serves as the main central hub or core point of coordination for another entity or set of entities.
-
E.
primaryDomain
Indicates that one domain is the main or most important domain associated with an entity, as opposed to any secondary or alternate domains.
- F. None of above.
Provenance (4 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. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37410876448190b02420f3d667d073 |
completed | June 21, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:03 a.m.