Triple
T7388673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adobe Marketing Cloud |
E170445
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | marketing software suite |
C4106
|
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: marketing software suite Context triple: [Adobe Marketing Cloud, instanceOf, marketing software suite]
-
A.
marketing technology platform
chosen
A marketing technology platform is an integrated software system that centralizes, automates, and optimizes marketing activities across channels to improve targeting, execution, measurement, and ROI.
-
B.
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.
-
C.
Salesforce product
A Salesforce product is a configurable item or service offered by a business that can be sold, priced, and tracked within the Salesforce platform for quoting, ordering, and revenue management.
-
D.
enterprise portal software
Enterprise portal software is a centralized, web-based platform that integrates applications, data, and services to provide personalized, secure access and collaboration tools for employees, partners, and customers across an organization.
-
E.
omnichannel customer service platform
An omnichannel customer service platform is a unified system that enables businesses to manage and respond to customer interactions seamlessly across multiple channels (such as email, chat, social media, phone, and SMS) from a single interface.
- 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_69c68a5e2c9081909e713ce866e0060a |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:09 p.m.