Triple
T22322488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zope Public License |
E551821
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | non-GPL-compatible license |
C17178
|
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: non-GPL-compatible license Context triple: [Zope Public License, instanceOf, non-GPL-compatible license]
-
A.
copyleft-incompatible license
chosen
A copyleft-incompatible license is a software license whose terms prevent code under it from being combined or distributed with code governed by a copyleft license without violating one or both licenses’ conditions.
-
B.
copyleft-compatible license
A copyleft-compatible license is a software license whose terms allow its code to be combined and redistributed with copyleft-licensed code without violating the copyleft license’s requirements.
-
C.
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.
-
D.
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.
-
E.
standardized license
A standardized license is a pre-defined, widely accepted legal agreement that sets uniform terms and conditions for using, sharing, or distributing a product, service, or intellectual property.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:42 p.m.