Triple
T18506508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Net Promoter Score |
E452210
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | customer experience metric |
C31098
|
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: customer experience metric Context triple: [Net Promoter Score, instanceOf, customer experience metric]
-
A.
user experience platform
A user experience platform is an integrated system that enables organizations to design, deliver, measure, and optimize consistent, personalized, and intuitive interactions across all digital touchpoints.
-
B.
customer success platform
A customer success platform is a software solution that centralizes customer data, tracks engagement and health metrics, and orchestrates proactive workflows to help businesses retain and grow their customer base.
-
C.
employee experience app
An employee experience app is a digital platform that centralizes communication, feedback, recognition, resources, and workplace services to improve employees’ daily work life and engagement.
-
D.
evaluation metric
chosen
An evaluation metric is a quantitative measure used to assess the performance, quality, or effectiveness of a model, system, or process against defined criteria or ground truth.
-
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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:36 a.m.