Triple
T28124546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenText Core Share |
E710890
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cloud-based content collaboration platform |
C9207
|
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: cloud-based content collaboration platform Context triple: [OpenText Core Share, instanceOf, cloud-based content collaboration platform]
-
A.
enterprise collaboration product
An enterprise collaboration product is a software platform that enables employees and teams within an organization to communicate, share information, and coordinate work efficiently and securely.
-
B.
collaborative online platform
chosen
A collaborative online platform is a digital environment that enables multiple users to work together in real time or asynchronously by sharing information, coordinating tasks, and communicating through integrated tools and services.
-
C.
content lifecycle management tool
A content lifecycle management tool is a system that plans, creates, organizes, distributes, tracks, and archives content across its entire lifespan to ensure consistency, compliance, and maximum impact.
-
D.
cloud-based application
A cloud-based application is software that runs on remote servers and is accessed over the internet, providing scalable, on-demand functionality without requiring local installation or infrastructure management.
-
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_69ef9b73bd288190a21ae3d6aa14f386 |
completed | April 27, 2026, 5:22 p.m. |
Created at: April 27, 2026, 9:19 p.m.