Triple
T14155483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HealthShare NSW |
E350804
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | shared services organization |
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 organization Context triple: [HealthShare NSW, instanceOf, shared services organization]
-
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.
application service organization
An application service organization is a business entity that delivers software applications and related IT services to clients, typically over a network, managing deployment, maintenance, and support on their behalf.
-
C.
digital services organization
A digital services organization is an entity that designs, builds, and operates technology-enabled solutions—such as software platforms, applications, and online services—to deliver value and outcomes for customers and stakeholders.
-
D.
technical services organization
A technical services organization is a specialized entity that provides expert engineering, IT, and other technology-focused support, solutions, and maintenance to help clients design, implement, and operate complex systems.
-
E.
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.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 12:58 a.m.