Triple
T8618390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zoho Sheet |
E204099
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cloud-based spreadsheet application |
C23215
|
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: cloud-based spreadsheet application Context triple: [Zoho Sheet, instanceOf, cloud-based spreadsheet application]
-
A.
cloud-based application
chosen
A cloud-based application is software that runs on remote servers and is accessed over the internet, providing scalable, on-demand functionality without requiring local installation or infrastructure management.
-
B.
cloud storage service
A cloud storage service is an online platform that securely stores, syncs, and manages users’ digital files on remote servers, enabling access and sharing from any internet-connected device.
-
C.
enterprise software-as-a-service platform
An enterprise software-as-a-service platform is a cloud-based solution that delivers scalable, secure, and centrally managed business applications to organizations on a subscription basis.
-
D.
cloud computing platform
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.
collaborative online platform
A collaborative online platform is a digital environment that enables multiple users to work together in real time or asynchronously by sharing information, coordinating tasks, and communicating through integrated tools and services.
- 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_69ca832ceab8819096e4a9f546695079 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:26 p.m.