Triple
T5895312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MPL 2.0 |
E131086
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | file-level copyleft license |
C246
|
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: file-level copyleft license Context triple: [MPL 2.0, instanceOf, file-level copyleft license]
-
A.
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.
-
B.
public copyright license
chosen
A public copyright license is a legal agreement by which a copyright holder grants the general public advance permission to use, share, and sometimes modify a work under specified conditions without needing to request individual authorization.
-
C.
copyleft-incompatible license
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.
-
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
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_69c00857439c819095950754176aa58a |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:58 p.m.