Triple
T21419950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office core technologies |
E528408
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | application infrastructure |
C44750
|
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: application infrastructure Context triple: [Office core technologies, instanceOf, application infrastructure]
-
A.
application delivery platform
An application delivery platform is a comprehensive system that manages, optimizes, secures, and scales the delivery of applications to end users across diverse networks and devices.
-
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.
application management system
An application management system is a software platform that streamlines the end-to-end process of receiving, tracking, evaluating, and managing applications and related communications.
-
D.
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.
-
E.
data application platform
A data application platform is an integrated environment that enables users to ingest, store, process, analyze, and operationalize data to rapidly build, deploy, and manage data-driven applications at scale.
- F. None of above. chosen
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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 5:47 p.m.