Triple
T29865608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Innovapost |
E758446
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | shared services provider |
C11050
|
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: shared services provider Context triple: [Innovapost, instanceOf, shared services provider]
-
A.
shared service centre
chosen
A shared service centre is a centralized organizational unit that consolidates and delivers common support functions (such as finance, HR, or IT) to multiple business units to improve efficiency, standardization, and cost-effectiveness.
-
B.
managed services provider
A managed services provider is a third-party company that proactively manages and supports an organization’s IT infrastructure, systems, and end-user services under a subscription or contract-based model.
-
C.
external service provider
An external service provider is an independent organization or individual contracted to deliver specific services or functions that support, supplement, or extend a client’s internal capabilities.
-
D.
support services company
A support services company provides specialized assistance and operational functions—such as customer service, technical support, maintenance, or administrative help—to enable other organizations to run more efficiently and focus on their core activities.
-
E.
professional services solutions provider
A professional services solutions provider is an organization that delivers specialized expertise, advisory, and implementation services to help clients solve complex business challenges and achieve strategic objectives.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:51 p.m.