Triple
T21169886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PeopleSoft Process Scheduler |
E521663
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | PeopleSoft component |
C44296
|
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: PeopleSoft component Context triple: [PeopleSoft Process Scheduler, instanceOf, PeopleSoft component]
-
A.
Oracle Fusion Middleware component
An Oracle Fusion Middleware component is a modular software element within Oracle's middleware platform that provides specific services—such as integration, security, or application hosting—to support and connect enterprise applications.
-
B.
Lotus Domino component
A Lotus Domino component is a modular software element within the IBM Lotus Domino platform that provides specific messaging, application, or directory services to support collaborative and enterprise applications.
-
C.
enterprise portal software
Enterprise portal software is a centralized, web-based platform that integrates applications, data, and services to provide personalized, secure access and collaboration tools for employees, partners, and customers across an organization.
-
D.
software component model
A software component model is a conceptual framework that defines how modular, reusable software units are specified, composed, and interact within a system.
-
E.
groupware infrastructure component
A groupware infrastructure component is a foundational software or service module that provides shared communication, coordination, and data-management capabilities to support collaborative applications and multi-user work environments.
- 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_69e0b50e30748190b186824a206d39b9 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3 p.m.