Triple
T4443052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruby License |
E96216
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | copyleft-compatible 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: copyleft-compatible license Context triple: [Ruby License, instanceOf, copyleft-compatible license]
-
A.
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.
-
B.
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.
-
C.
public copyright license
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.
-
D.
Creative Commons program
A Creative Commons program is an initiative or software tool designed to facilitate the use, creation, and sharing of works under Creative Commons licenses by providing legal, educational, or technical support for open licensing.
-
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. 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:32 p.m.