Triple
T28627041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wikimedia Cloud Services |
E724552
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hosting platform |
C5173
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: hosting platform Context triple: [Wikimedia Cloud Services, instanceOf, hosting platform]
-
A.
self-hosting platform
A self-hosting platform is a system that enables users to deploy, manage, and maintain their own software services and infrastructure on servers they control, rather than relying on third-party hosting providers.
-
B.
server hosting service
A server hosting service provides and manages remote computing resources, including hardware, networking, storage, and uptime, so clients can deploy and run applications, websites, or services without maintaining physical infrastructure.
-
C.
fiction hosting service
A fiction hosting service is an online platform that allows users to upload, share, discover, and read original written stories, often with tools for organizing, rating, and commenting on works.
-
D.
cloud computing platform
chosen
A cloud computing platform is an integrated environment that provides on-demand access to scalable computing resources, storage, and services over the internet, enabling users to deploy, manage, and run applications without managing underlying hardware.
-
E.
documentation hosting platform
A documentation hosting platform is an online service that stores, organizes, and presents technical or user-facing documentation, often with features for versioning, search, collaboration, and integration with development workflows.
- F. None of above.
Provenance (1 batch)
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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 4:36 a.m.