Triple
T30802513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APL (AROS Public License) |
E784408
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | AROS-specific software license |
C57231
|
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: AROS-specific software license Context triple: [APL (AROS Public License), instanceOf, AROS-specific software 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.
proprietary license
A proprietary license is a legal agreement that grants users limited rights to use, but not freely modify or redistribute, software or other intellectual property owned and controlled by a specific individual or organization.
-
C.
source-available license
A source-available license is a software license that allows users to view and sometimes modify the source code but does not meet all the criteria of open-source or free software licenses, often imposing additional restrictions on use, distribution, or modification.
-
D.
custom license
A custom license is a tailored legal agreement that defines specific permissions, restrictions, and conditions for using, modifying, and distributing a particular work or resource.
-
E.
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.
- F. None of above. chosen
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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:42 p.m.