Triple
T27586251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM Watson Discovery |
E699695
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | AI-powered search product |
C5163
|
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: AI-powered search product Context triple: [IBM Watson Discovery, instanceOf, AI-powered search product]
-
A.
search engine brand
A search engine brand is a distinct identity and reputation associated with a specific web search service that users recognize, trust, and choose for finding information online.
-
B.
OpenAI product
An OpenAI product is a software or service offering that applies OpenAI’s artificial intelligence models and technologies to solve specific user or business problems in a reliable, scalable, and user-friendly way.
-
C.
comparison shopping service
A comparison shopping service is an online platform that aggregates product information and prices from multiple retailers to help consumers easily compare options and find the best deals.
-
D.
enterprise AI product
chosen
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.
-
E.
Yahoo! product
A Yahoo! product is any digital service, application, or platform developed, branded, or operated by Yahoo! to provide online content, communication, search, or advertising functionality to users.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
Created at: April 27, 2026, 2:04 p.m.