Triple
T27587576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murano |
E699722
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cloud application catalog |
C31297
|
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 application catalog Context triple: [Murano, instanceOf, cloud application catalog]
-
A.
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.
-
B.
online software catalog
chosen
An online software catalog is a web-based system that organizes, describes, and provides access to a curated collection of software applications, enabling users to search, compare, and obtain software products efficiently.
-
C.
cloud-native application
A cloud-native application is a software system designed and built specifically to run in cloud environments, leveraging microservices, containers, dynamic orchestration, and continuous delivery to achieve scalability, resilience, and rapid iteration.
-
D.
composite application platform
A composite application platform is an integrated environment that enables the rapid assembly, orchestration, and management of multiple independent services or components into unified, end-to-end business applications.
-
E.
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.
- 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
Created at: April 27, 2026, 2:04 p.m.