Triple
T14370806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nextcloud Calendar |
E356353
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | self-hosted groupware component |
C33870
|
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: self-hosted groupware component Context triple: [Nextcloud Calendar, instanceOf, self-hosted groupware component]
-
A.
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.
-
B.
groupware
Groupware is collaborative software that enables multiple users to work together, communicate, and share information in real time or asynchronously, often across different locations.
-
C.
self-hosting platform
A self-hosting platform is a system that enables users to deploy, manage, and maintain their own software services and infrastructure on servers they control, rather than relying on third-party hosting providers.
-
D.
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.
-
E.
GNOME component
A GNOME component is a modular software element within the GNOME desktop environment that provides specific functionality or services, such as panels, applets, libraries, or system tools, to create a cohesive user experience.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:15 a.m.