Triple
T10167700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expat License |
E235248
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | permissive software 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: permissive software license Context triple: [Expat License, instanceOf, permissive software license]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 9:10 p.m.