Triple
T4325087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open Source Initiative |
E96618
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 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: software advocacy organization Context triple: [Open Source Initiative, instanceOf, 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.
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.
-
C.
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.
-
D.
software freedom activist
A software freedom activist is an individual who advocates for users’ rights to run, study, modify, and share software freely, promoting open-source principles and resisting restrictive digital controls.
-
E.
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.
- 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_69b34542fd908190b11b08faad8decfd |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:13 p.m.