Triple
T4330873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ChatGPT |
E96744
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | conversational AI system |
C4098
|
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: conversational AI system Context triple: [ChatGPT, instanceOf, conversational AI system]
-
A.
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.
-
B.
automatic speech recognition system
An automatic speech recognition system converts spoken language into written text by analyzing and interpreting audio signals using acoustic, linguistic, and statistical models.
-
C.
virtual assistant
chosen
A virtual assistant is an AI-powered software agent that interacts with users through natural language to perform tasks, answer questions, and provide personalized support across digital platforms.
-
D.
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.
-
E.
enterprise AI product
An enterprise AI product is a scalable, secure software solution that embeds artificial intelligence into business workflows to automate tasks, augment decision-making, and deliver measurable operational and strategic value across an organization.
- 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_69b34542fd908190b11b08faad8decfd |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:13 p.m.