Triple
T15098201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google Play ecosystem |
E360595
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | digital distribution ecosystem |
C4407
|
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: digital distribution ecosystem Context triple: [Google Play ecosystem, instanceOf, digital distribution ecosystem]
-
A.
digital distribution platform
chosen
A digital distribution platform is an online system that delivers digital content—such as software, games, media, or documents—to users over the internet, handling discovery, purchase, licensing, and delivery.
-
B.
digital platform
A digital platform is an online infrastructure that facilitates interactions, transactions, or value exchange between users, services, or systems through integrated digital tools and interfaces.
-
C.
software and services ecosystem
A software and services ecosystem is an interconnected network of applications, platforms, tools, and providers that collaboratively deliver integrated digital capabilities and value to users and organizations.
-
D.
global distribution system provider
A global distribution system provider is a company that operates a computerized network enabling transactions between travel service suppliers (such as airlines, hotels, and car rental companies) and travel agencies or end customers worldwide.
-
E.
gaming ecosystem
A gaming ecosystem is an interconnected network of platforms, hardware, software, communities, and services that collectively enable the creation, distribution, monetization, and play of video games.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:04 a.m.