Triple
T22503570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3DEXPERIENCE |
E556334
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | product lifecycle management platform |
C27377
|
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: product lifecycle management platform Context triple: [3DEXPERIENCE, instanceOf, product lifecycle management platform]
-
A.
product lifecycle management software
chosen
Product lifecycle management software is an integrated digital system that manages and connects all data, processes, and stakeholders involved in a product’s journey from initial concept and design through manufacturing, service, and end-of-life.
-
B.
application lifecycle management platform
An application lifecycle management platform is an integrated system that supports planning, development, testing, deployment, maintenance, and governance of software applications throughout their entire lifecycle.
-
C.
life cycle management center
A life cycle management center is an organizational unit that oversees, coordinates, and optimizes all phases of a product’s or system’s life cycle—from conception and development through deployment, maintenance, and disposal—to ensure efficiency, compliance, and value realization.
-
D.
business platform
A business platform is an integrated digital environment that connects organizations, partners, and customers to enable core business processes, data exchange, and value creation at scale.
-
E.
enterprise software-as-a-service platform
An enterprise software-as-a-service platform is a cloud-based solution that delivers scalable, secure, and centrally managed business applications to organizations on a subscription basis.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:50 p.m.