Triple
T22702595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mozilla Public License |
E561361
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | FOSS license |
C15651
|
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: FOSS license Context triple: [Mozilla Public License, instanceOf, FOSS 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.
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.
-
D.
copyleft-compatible license
chosen
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.
-
E.
freeware license
A freeware license is a software license that allows users to use a program at no monetary cost, while typically retaining the author's copyright and imposing certain usage or redistribution conditions.
- 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_69e2454e615481909c177440be559d2c |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:16 p.m.