Triple
T26373068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adobe Target |
E660822
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | personalization platform |
C13271
|
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: personalization platform Context triple: [Adobe Target, instanceOf, personalization platform]
-
A.
personalization tool
chosen
A personalization tool is a system or application that tailors content, experiences, or functionality to individual users based on their preferences, behavior, and contextual data.
-
B.
intelligent personal assistant
An intelligent personal assistant is a software agent that uses artificial intelligence to understand user requests, manage tasks, and provide personalized information or services through natural language interaction.
-
C.
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.
-
D.
business platform
A business platform is an integrated digital environment that connects organizations, partners, and customers to enable core business processes, data exchange, and value creation at scale.
-
E.
online personal styling service
An online personal styling service is a digital platform that curates and recommends clothing and accessories tailored to an individual’s preferences, body type, and lifestyle, often using stylist expertise and/or algorithms.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 10:59 p.m.