Triple
T34627778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Software Freedom Conservancy |
E889186
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | free and open source software advocacy organization |
C13213
|
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 advocacy organization Context triple: [Software Freedom Conservancy, instanceOf, free and open source software advocacy organization]
-
A.
open-source organization
chosen
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.
-
B.
free software advocacy project
A free software advocacy project is an organized effort that promotes the use, development, and protection of software that respects users’ freedom to run, study, modify, and share it.
-
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.
free software advocate
A free software advocate is someone who actively promotes the use, development, and protection of software that grants users the freedoms to run, study, modify, and share it.
- 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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:04 a.m.