Triple
T36641703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenSSF |
E904602
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | open source security 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: open source security organization Context triple: [OpenSSF, instanceOf, open source security 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.
Internet Security Research Group
The Internet Security Research Group is a nonprofit organization dedicated to improving internet security by promoting and providing accessible, open, and automated security technologies and practices.
-
C.
open-source intelligence collective
An open-source intelligence collective is a collaborative group that gathers, analyzes, and shares publicly available information to produce actionable insights for research, security, or advocacy purposes.
-
D.
open source company
An open source company is a business that develops, maintains, and often monetizes software whose source code is publicly available for use, modification, and distribution under open source licenses.
-
E.
open source program office
An open source program office is a centralized organizational function that defines policies, provides guidance, and manages processes for the strategic use, contribution to, and governance of open source software within an organization.
- 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:11 p.m.