Triple
T24929798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open Software License 2.1 |
E618953
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | open source license |
C13246
|
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 license Context triple: [Open Software License 2.1, instanceOf, open source license]
-
A.
OSI-approved license
An OSI-approved license is a software license that has been reviewed and certified by the Open Source Initiative as complying with its Open Source Definition, ensuring users' rights to freely use, modify, and distribute the software.
-
B.
family of free software licenses
A family of free software licenses is a group of related legal frameworks that grant users the freedom to use, study, modify, and redistribute software, often with varying conditions on how derivative works are shared.
-
C.
open data license
An open data license is a legal framework that grants users permission to freely access, use, modify, and share data, typically under conditions such as attribution and share-alike.
-
D.
open content license
An open content license is a legal framework that allows creators to grant the public permission to use, share, and often modify their work under specified conditions, typically to promote free access and collaboration.
-
E.
permissive free software license
chosen
A permissive free software license is a type of open-source license that allows users to freely use, modify, and redistribute the software with minimal restrictions, typically requiring only attribution and preservation of the license notice.
- 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_69e2fab9edd88190b86004a78a28bc20 |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 5:29 a.m.