Triple
T9017964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KDE community |
E215643
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | free and open-source software community |
C8513
|
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: free and open-source software community Context triple: [KDE community, instanceOf, free and open-source software community]
-
A.
free software community
chosen
A free software community is a collaborative group of users and developers who create, share, and improve software whose source code is openly available and can be freely used, modified, and redistributed.
-
B.
open-source organization
An open-source organization is a collaborative entity that develops, maintains, and governs software or other projects whose source materials are publicly accessible, modifiable, and distributable under open licenses.
-
C.
open-source software advocate
An open-source software advocate is a person who actively promotes the use, development, and principles of open-source software, emphasizing transparency, collaboration, and community-driven innovation.
-
D.
open-source advocate
An open-source advocate is a person who actively promotes, supports, and contributes to freely accessible, collaboratively developed software and open standards, emphasizing transparency, community, and shared innovation.
-
E.
open source contributor
An open source contributor is an individual who voluntarily improves, maintains, or supports publicly available software or documentation by submitting code, reporting issues, reviewing changes, or providing other collaborative input.
- 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_69ca83a38aa88190bf1bb80c4548b5e2 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 7:07 p.m.