Triple
T5934397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teleperformance |
E132008
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | customer experience management company |
C423
|
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 management company Context triple: [Teleperformance, instanceOf, customer experience management company]
-
A.
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.
-
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.
corporate travel management company
A corporate travel management company is a specialized service provider that plans, books, and oversees business travel for organizations to optimize cost, compliance, and traveler experience.
-
D.
company
chosen
A company is an organized entity, legally recognized or informally structured, that coordinates people and resources to produce goods or services for customers, typically in pursuit of profit or specific objectives.
-
E.
computer services company
A computer services company is an organization that provides technical expertise, support, and solutions related to computer systems, software, networks, and IT infrastructure for individuals or other businesses.
- 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_69c0085c55dc8190aa90e242c956e2fa |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 4 p.m.