Triple
T15600176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Shared Services Center |
E375009
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | shared services center |
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 center Context triple: [NASA Shared Services Center, instanceOf, shared services center]
-
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.
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.
-
C.
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.
-
D.
public service system
A public service system is an organized framework of institutions, processes, and resources designed to deliver essential services and support to the public in an efficient, equitable, and transparent manner.
-
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_69d85cce25008190b13b52745fbd719b |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:12 a.m.